@chikara I have received two site notifications, not only to me but the entire Staff team here at Qoto. (I am not yet a member of staff, although have been nominated for a position).

I underrstand you want to make your point well, but to post a large message that is in regards to the whole instance admin and mod staff, and then pull it off - twice - is not a proper way to do it.

Please write a draft and post it.

Or better yet, open a topic in our Moderation subforum in the Qoto Discourse Forums.

https://discourse.qoto.org/c/QOTO/moderation

User registration is required, but just takes a minute.

I dropped other work to come and check, twice, and was half way thru a long legal and semantic argument you were positing.

@freemo @arteteco @Surasanji @mngrif

@design_RG I proofread each post as best I can, but there is only very small print in a narrow newspaper-like column on the left of the screen.

Then when I post what I think is error-free, the font is larger. Then I see mistakes that were not obvious before.

And so, I use the delete and re-write option immediately. Also, this is the way I identify and correct format errors.

Isn't this what the QOTO system was designed for everyone to do?

@chikara Thank you for your reply, and yes, the process works as you described in general.

Although there are BETTER ways to do long posts, which I do use here and elsewhere.

I am with you 100% in considering the Toot Editor box too small for serious posting - and use a plain text editor on my laptop instead to compose larger pieces.

That gives me full screen capability, a spell checker if desired, and once I am happy, a cut and paste into the tiny Toot editor box will send it into the fediverse.

In smaller posts and *specially* if I am not tagging other users (which will fire up notification to them instantly), I used delete/Redraft and fix small errors as needed.

With people being called in, that is less optimal.

When I make a post and address a whole site's Staff team -- and then take the post away from them while they read it, it's less proper.

Not to use the word annoying, which in fact I consider it is.

We welcome dialogue, but addressing the whole crew, raising issues is not casual posting.

@chikara Forgot to invite @freemo into this.

@design_RG

Keep in mind he is only asking you try to proofread before posting in order to create less notification noise. If you post something and decide you need to edit it you are welcome to do so, dont feel it is an issue. But if you can catch the errors before hand it would just be nice for others since it can be annoying to see messages pop in and out of existance.

What your doing is fine though, just be aware of the mechanics and if you can try to minimize the noise is all.

@chikara

@freemo

Exactly. It was specially hard on me when the post in question is not a casual banter, but a question of order and a call for the whole staff team.
@chikara