User talk:87.196.82.31

Attention: Last edited: Last edited by: 18:06, 11 July 2022 (UTC) Alexf (talk · contribs) This IP address, 87.196.82.31, is registered to NOS Comunicaçoes S.A., Portugal. In the event of persistent vandalism from this address, efforts may be made to contact them to report abuse. Contact information may be available in the WHOIS report. If you are editing from this IP address and are frustrated by irrelevant messages, you can avoid them by creating an account for yourself. Sometimes, in response to vandalism, you may be temporarily unable to create an account. If you are an unregistered user operating from this address, note that it may be possible for the owner of the IP to determine who was making contributions from this address at any given time. If you are the owner of this address responding to reports of inappropriate conduct from this address, you may find the contributions history and block log for this address helpful. Please feel free to contact any administrator who has blocked this address with questions (blocking admins will be listed in the block log).

Hello, I'm Sam Walczak. I wanted to let you know that one or more of your recent contributions have been undone because they did not appear constructive. If you would like to experiment, please use the sandbox. If you have any questions, you can ask for assistance at the Teahouse or the Help desk. Thanks. Sam Walczak^Talk/_Edits 19:49, 10 July 2022 (UTC)[reply]

If you are deleting the articles and creating a redirect because you believe the content should be deleted, it has been contested, please follow the process for when a blank and redirect is challenged. FrederalBacon (talk) 19:53, 10 July 2022 (UTC)[reply]

You may be blocked from editing without further warning the next time you vandalize Wikipedia, as you did at Jungle Love (Family Guy). Stop redirecting. It has been challenged. Discuss in the talk. Next step is ARV. FrederalBacon (talk) 20:44, 10 July 2022 (UTC)[reply]

Your recent editing history at Jungle Love (Family Guy) 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 blocked from editing—especially if you violate the three-revert rule, which states that an editor must not perform more than three reverts on a single page within a 24-hour period. Undoing another editor's work—whether in whole or in part, whether involving the same or different material each time—counts as a revert. Also keep in mind that while violating the three-revert rule often leads to a block, you can still be blocked for edit warring—even if you do not violate the three-revert rule—should your behavior indicate that you intend to continue reverting repeatedly. Nythar (talk) 01:47, 11 July 2022 (UTC)[reply]

I again ask, what is up with the redirects for those two episodes specifically? They keep getting reverted by multiple editors, you keep putting them back up. What is going on? FrederalBacon (talk) 17:49, 11 July 2022 (UTC)[reply]

You have been blocked from editing for a period of 48 hours to prevent further vandalism. Once the block has expired, you are welcome to make useful contributions.

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 ~~~~}}.  Alexf^(talk) 18:05, 11 July 2022 (UTC)[reply]