Click here to leave a message... This talk page is archived manually on the 15th day of every month, when the previous month's conversations are filed into storage. This applies unless it would lead to no conversations being left. If the user switches to bot-based archiving, the account has been compromised. Send help.
Personally I agree with Favonian that we shouldn't be wasting our time processing requests from a likely sock, but on the other hand I don't particularly care whether or not swimming is protected at this time. If this user starts filling up RFPP again with pointless requests I will likely block them however. OhNoitsJamieTalk02:44, 12 June 2024 (UTC)Reply
Honestly typing, that is what I planned to do in the future, but compiling the pages in one edit like this one, nonetheless excluding media-related articles given the fact that the LTA case in my region being prevalent. But seriously, I was making requests mainly because of two reasons: 1)Page protector is inactive, and 2)Page is protected long enough (provided that it doesn't have a lengthy list of protection history). Why are you considering my case "pointless"? If you believe they are "pointless", then why did you accept my request for unprotecting pool (cue sports) in the first place?102.156.121.163 (talk) 07:14, 12 June 2024 (UTC)Reply
@Ohnoitsjamie: These requests are pretty valid from a policy point of view and are not what I would call pointless (I could get that perspective if they were requesting semi-protection removals for redirects, but these are "live" pages that have very little need for continued protection). I hope that the link between the LTA and these IPs isn't just being made because they're from Tunisia, given that this IP doesn't fit into the behavioural clues listed at the LTA page regarding lack of communication. Sdrqaz (talk) 15:43, 12 June 2024 (UTC)Reply
Not only "lacking communication skills", but also persistent reverts. Users might have mistaken me an LTA user by accounting my reverts to this edit as well as this edit. I am currently decreasing my activity for a while, as a means of accepting the wp:so, provided that one of my ranges is meant to be blocked for 3 months.
I find out that negotiating issues with experienced editors interesting. However, there is one thing I intend to avoid but also uncertain if I am ever commiting it (if it is, I am sorry to type this) and that is: wp:hounding. I understand such behaviour leads to serious consequences/sanctions, but how can anyone tell if I am ever commiting it? (see also user talk:el C)102.156.121.163 (talk) 16:47, 12 June 2024 (UTC)Reply
I realized you did not remove or shorten protection from one of the pages. Since I have made that request again at user talk:lectonar, I am unlikely that I would request that again given that he explained why indefinite protection is still necessary, albeit being protected for over five years.102.156.121.163 (talk) 07:14, 12 June 2024 (UTC)Reply
The difference being that you down-protected almost all of them from semi to pending (actually that's also my take, downgrade to pending with time-limit, to evaluate the effect of it) whereas the Big brother ones are only pending changes protected to start with, afaics, and are still experiencing disruption on a lower level. Lectonar (talk) 07:19, 13 June 2024 (UTC)Reply
True, but when there are on average only two reverted edits by non-autoconfirmed users in the past year, the need for continued protection is not as pronounced. Sdrqaz (talk) 21:51, 13 June 2024 (UTC)Reply
Hi, RegierungDavidlands1852. I removed some personal information from your user page, including information about your location. The material was suppressed, meaning that the information was removed from public view, with administrators also unable to access it (only members of the Oversight team can).
This was done to prevent possible harassment; you may find this useful. As there is still some personal information on your user page, you may want to remove some of that too after reading the link above. Sdrqaz (talk) 23:41, 5 July 2024 (UTC)Reply