User talk:Mouyong65

Hi Mouyong65! I noticed that you have reverted to restore your preferred version of Gallery of sovereign state flags several times. The impulse to undo an edit you disagree with is understandable, but I wanted to make sure you're aware that the edit warring policy disallows repeated reversions even if they are justifiable.

All editors are expected to discuss content disputes on article

Your recent editing history at Gallery of sovereign state flags shows that you are currently engaged in an edit war; that means that you are repeatedly changing content back to how you think it should be, when you have seen that other editors disagree. To resolve the content dispute, please do not revert or change the edits of others when you are reverted. Instead of reverting, please use the talk page to work toward making a version that represents consensus among editors. The best practice at this stage is to discuss, not edit-war. See the bold, revert, discuss cycle for how this is done. If discussions reach an impasse, you can then post a request for help at a relevant noticeboard or seek dispute resolution. In some cases, you may wish to request temporary page protection.

Being involved in an edit war can result in you being

]

Notice of edit warring noticeboard discussion

Hello. This message is being sent to inform you that there is currently a discussion involving you at Wikipedia:Administrators' noticeboard/Edit warring regarding a possible violation of Wikipedia's policy on edit warring. The thread is Wikipedia:Administrators' noticeboard/Edit warring#User:Mouyong65 reported by User:Chipmunkdavis (Result: ). Thank you. CMD (talk) 10:23, 28 March 2022 (UTC)[reply]

March 2022

You have been blocked indefinitely from editing for persistently making disruptive edits.

If you think there are good reasons for being unblocked, please read the guide to appealing blocks, then add the following text below the block notice on your talk page: {{unblock|reason=Your reason here ~~~~}}.  Bbb23 (talk) 12:04, 28 March 2022 (UTC)[reply]