Jump to content

User talk:82.4.73.190

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Unblock request

[edit]
This user's unblock request has been reviewed by an administrator, who declined the request. Other administrators may also review this block, but should not override the decision without good reason (see the blocking policy).

82.4.73.190 (block log • active blocks • global blocks • contribs • deleted contribs • filter log • creation log • change block settings • unblock • checkuser (log))

Request reason:

I have absolutely no idea why I've been blocked: I've only made a few contributions, cleaning up very minor typos/grammar, which don't seem to be contentious as none of them have been reverted. WP:HUMAN appears to cover this: I seem to have been blocked proactively, and if there's any reason other than simply being unregistered then I'm unaware of it. The block reason certainly wasn't enlightening. I don't intend to register, after having been disillusioned when I lost my account when the various wikis merged (Dislogical~enwiki, though when I used it it was just Dislogical. Only one edit shows, which is inexplicable as I made several)

Decline reason:

Hello IP 82.4.73.190. This address is not currently blocked. Unfortunately, the IP range in question is a favorite haunt for a notorious editor who has been banned for persistent disruption. The range has been blocked more than 40 times over the years. The best way to avoid being caught in an IP range block is to register for a WP:ACCOUNT. It's easy, free and has a number of advantages beyond avoiding IP blocks, including the ability to edit pages that may be subject to editing restrictions and the ability to create new pages. I apologize for the inconvenience. -Ad Orientem (talk) 17:42, 15 January 2025 (UTC)[reply]

If you want to make any further unblock requests, please read the guide to appealing blocks first, then use the {{unblock}} template again. If you make too many unconvincing or disruptive unblock requests, you may be prevented from editing this page until your block has expired. Do not remove this unblock review while you are blocked.

Ad Orientem (talk) 17:42, 15 January 2025 (UTC)}}[reply]

Hi IP, it doesn't look like you're blocked. Can you tell us the exact block message you're receiving? I agree that there's nothing wrong with your edits. -- asilvering (talk) 16:05, 15 January 2025 (UTC)[reply]
Apologies for the format, I'm not sure how to reproduce the box or if I can put a acreenshot inline, but a copy and paste of the text when I try to edit is as follows:
This IP address has been blocked from editing Wikipedia.
This does not affect your ability to read Wikipedia pages.
Most people who see this message have done nothing wrong. Some kinds of blocks restrict editing from specific service providers or telecom companies in response to recent abuse or vandalism, and can sometimes affect other users who are unrelated to that abuse. Review the information below for assistance if you do not believe that you have done anything wrong.
The IP address or range 82.132.192.0/18 has been blocked by ‪Ad Orientem‬ for the following reason(s):
To edit, please log in.
Editing by unregistered users from your shared IP address or address range may be currently disabled due to abuse. However, you are still able to edit if you sign in with an account. If you are currently blocked from creating an account, and cannot create one elsewhere in the foreseeable future, you may follow the instructions at Wikipedia:Request an account to request that volunteers create your username for you. Please use an email address issued to you by your ISP, school or organization so that we may verify that you are a legitimate user on this network. Please reference this block in the comment section of the form.
Please check on this list that the username you choose has not already been taken. We apologize for any inconvenience.
LTA WP:BKFIP
This block will expire on 20:34, 4 September 2025. Your current IP address is 82.4.73.190.
Even when blocked, you will usually still be able to edit your user talk page, as well as email administrators and other editors.
For information on how to proceed, please read the FAQ for blocked users and the guideline on block appeals. The guide to appealing blocks may also be helpful.
Other useful links: Blocking policy · Help:I ha
I hope that helps? 82.4.73.190 (talk) 16:10, 15 January 2025 (UTC)[reply]
Okay, this definitely isn't a response to your edits, and I am confident you're not the person that rangeblock is trying to stop. What I don't understand is how you're getting caught in that range. Can you humour me and try to make an edit somewhere other than this talk page right now and tell me if you get the same block message? -- asilvering (talk) 16:20, 15 January 2025 (UTC)[reply]
Certainly! I've had the same message on any page other than this one, including Joseph Aoun (disambiguation) and Wow! signal. I don't have any intended edits for those pages, I just thought it would cover a wide base to check. 82.4.73.190 (talk) 16:26, 15 January 2025 (UTC)[reply]
Alright, I don't get it. I'll find someone who knows more about IP blocks to come have a look. -- asilvering (talk) 16:57, 15 January 2025 (UTC)[reply]
(edit conflict) I do! Haha. The IP address range, which this IP address is within, is blocked due to a now-community banned editor utilising the address range for their disruptive ways for an extended period of time. Such range block is not done lightly as there can be collateral damage, like in this case, and it is done when the blocking admin is confident that there aren't many useful edits coming from the IP address range during the time the said editor was active. To lift the range block, @Ad Orientem will be the right person to process it as they are the blocking administrator.
Registered editors might not be blocked when logged in. As such please request for an account if you wish to continue editing from this IP address (hopefully!), or switch to another network/ISP if possible if you wish to continue editing without logging in. – robertsky (talk) 17:14, 15 January 2025 (UTC)[reply]
Yes, but @Robertsky, you'll notice this IP address is not in that range. -- asilvering (talk) 17:16, 15 January 2025 (UTC)[reply]
huh. how di I missed that. hmm. – robertsky (talk) 17:20, 15 January 2025 (UTC)[reply]
It is at least some relief that the people who understand IP addresses more than I do are also confused, haha. -- asilvering (talk) 17:24, 15 January 2025 (UTC)[reply]
Humour me as you had with @Asilvering, to the IP editor, can you clear the cookies for website and try editing? – robertsky (talk) 17:31, 15 January 2025 (UTC)[reply]
Thank you both for looking into this: clearing cookies didn't help unfortunately, the first time just gave an additional welcome popup along with the blocked message. 82.4.73.190 (talk) 17:38, 15 January 2025 (UTC)[reply]
@Robertsky I don't suppose you have any more ideas? As you may see the unblock request has been denied on the grounds that I don't appear to be blocked, and the cited range doesn't actually cover me. If nothing else it's a curious and likely undesirable bug that I am, nonetheless, blocked. 82.4.73.190 (talk) 00:21, 16 January 2025 (UTC)[reply]
Are you editing on the same device as you are making these comments with?©Geni (talk) 17:07, 15 January 2025 (UTC)[reply]
I've been trying to today, yes. 82.4.73.190 (talk) 17:16, 15 January 2025 (UTC)[reply]
@82.4.73.190 Please see my note in response to your unblock request above. Best regards... -Ad Orientem (talk) 17:44, 15 January 2025 (UTC)[reply]
Thank you for reviewing the situation. Given the rationale I doubt there will be a different result, but as I understand the appeal page the reviewing admin should not be the same as the blocking admin? Does that not apply as I haven't been blocked directly, but instead seem to have been caught in the range? 82.4.73.190 (talk) 17:56, 15 January 2025 (UTC)[reply]
The decline in this case was procedural, as this IP address is not currently blocked. -If you wish to post an unblock request for the IP range you would need to post that on one of the talk pages within that specific range. Ad Orientem (talk) 19:07, 15 January 2025 (UTC)[reply]
It certainly is blocked, whether or not it's meant to be. Is there any way in which I can provide evidence in the form of screenshots, or otherwise? 82.4.73.190 (talk) 23:26, 15 January 2025 (UTC)[reply]
This is extremely odd. If you could copy and paste the exact text of the block notice you get when trying to edit, that would be helpful. Apologies for the slow response. I have been quite busy in the real world for the last couple of days. -Ad Orientem (talk) 02:27, 16 January 2025 (UTC)[reply]
It doesn't seem slow at all, please don't apologize! The issue has been looked at, without yet finding a solution, in the conversation above this too. The text is as follows:
This IP address has been blocked from editing Wikipedia.
This does not affect your ability to read Wikipedia pages.
Most people who see this message have done nothing wrong. Some kinds of blocks restrict editing from specific service providers or telecom companies in response to recent abuse or vandalism, and can sometimes affect other users who are unrelated to that abuse. Review the information below for assistance if you do not believe that you have done anything wrong.
The IP address or range 82.132.192.0/18 has been blocked by ‪Ad Orientem‬ for the following reason(s):
To edit, please log in.
Editing by unregistered users from your shared IP address or address range may be currently disabled due to abuse. However, you are still able to edit if you sign in with an account. If you are currently blocked from creating an account, and cannot create one elsewhere in the foreseeable future, you may follow the instructions at Wikipedia:Request an account to request that volunteers create your username for you. Please use an email address issued to you by your ISP, school or organization so that we may verify that you are a legitimate user on this network. Please reference this block in the comment section of the form.
Please check on this list that the username you choose has not already been taken. We apologize for any inconvenience.
LTA WP:BKFIP
This block will expire on 20:34, 4 September 2025. Your current IP address is 82.4.73.190.
Even when blocked, you will usually still be able to edit your user talk page, as well as email administrators and other editors.
For information on how to proceed, please read the FAQ for blocked users and the guideline on block appeals. The guide to appealing blocks may also be helpful.
Other useful links: Blocking policy · Help:I ha 82.4.73.190 (talk) 11:56, 16 January 2025 (UTC)[reply]
@Oshwah. When you have a minute, could you have a look at this? According to everything I am looking at 82.4.73.190 (talk · contribs · deleted contribs · logs · filter log · block user · block log) , this IP address is not currently blocked. However the user is reporting that they are. See the above discussion. -Ad Orientem (talk) 15:47, 16 January 2025 (UTC)[reply]
Hi Drmies. I am somewhat stumped by this. See above. (I had pinged Oshwah but they might be busy.) Is it possible that this IP may be caught in the rangeblock noted above and it's not showing up on the contrib page? I don't really want to downgrade the block for that range. Given the history (40+ previous blocks) I think it's justified. But if there is some kind of issue specific to this IP address, I don't know what it would be. Tech is not my strong suit. (I don't even like cars with an automatic transmission.) It's late here but I will check back in tomorrow. -Ad Orientem (talk) 05:43, 17 January 2025 (UTC)[reply]
Ha, Ad Orientem--don't ask me: ask a real expert, like L235, or NinjaRobotPirate, or maybe zzuuzz... Drmies (talk) 19:50, 17 January 2025 (UTC)[reply]
@Drmies: For what it's worth, I turned in my CU tool at the end of my ArbCom term. Thanks for thinking of me though; I appreciate the comment! Best, KevinL (aka L235 · t · c) 22:46, 17 January 2025 (UTC)[reply]
I know, KevinL, but I figured even without that tool you'd know more then me. ;) Drmies (talk) 03:35, 18 January 2025 (UTC)[reply]
@Drmies Ah, thanks. -Ad Orientem (talk) 20:10, 17 January 2025 (UTC) (Still trying to figure out electric pencil sharpeners.)[reply]

I came across something similar a few months ago. Original here, the followup may be slightly informative, or not.[1] I believe that my conclusion was that there's some caching going on, and that it's likely related to cookie blocks (see WP:AUTOBLOCK). I note here for the benefit of others, that this IP shows as belonging Virgin, and the blocked range shows as belonging to BT or O2 (depending how you look up these things). It's all the same company these days: Virgin Media O2. To the IP, if you can somehow stay away from Virgin's mobile or 5G networks, I'd try that. If you have access to another device, I'd try that. I'd also try properly clearing any relevant cookies and restarting the browser (again, probably). If that doesn't work, after waiting a bit, then it's possible we have a bug somewhere within the template or messaging system. What would be helpful is if you kept an eye on your IP address to let us know how or if you ended up on the notorious 82.132 range. -- zzuuzz (talk) 20:34, 17 January 2025 (UTC)[reply]

I can also potentially pull an ace from my sleeve (may or may not work), and that is ping the real expert around here, @Dreamy Jazz:. -- zzuuzz (talk) 23:41, 17 January 2025 (UTC)[reply]
IP, you got the A-team on your case here. For free! Drmies (talk) 03:35, 18 January 2025 (UTC)[reply]
When someone is affected by a range block, but they're not on that IP range, I would expect it's a) a bug in Mediawiki, b) a cookie block from when they were on the affected IP range, c) some kind of proxy or traffic routing that involves the blocked IP range, or d) a VPN. The first one would be tricky to identify. One could always try to file a Mediawiki bug report and see what happens. The second one should be easy to fix – just clear your cookies or toggle on private browsing. The third is also tricky, and I've given up trying to figure out how modern ISPs work. And that brings us to VPN services. Unfortunately, everyone swears they're not using a VPN. Half the time, it turns out they are, but they've forgotten (or didn't understand) that they had enabled it. NinjaRobotPirate (talk) 03:55, 18 January 2025 (UTC)[reply]
I don't know how many interested people this will notify, but the block has now fallen off. I feel I should ping @Ad Orientem in particular since he's probably the most affected secondary party. Thank you to everyone who looked into this, especially if someone, somewhere, had something they could do (I know I didn't fix this)!
Cookies were cleared previously to no effect, and I'm reasonably certain I'm not using a VPN on my phone. Maybe I'm in that "half the time" though? I'm not a tech expert. 82.4.73.190 (talk) 04:05, 18 January 2025 (UTC)[reply]
Very glad to hear you are now free of any impediment. Do give some thought to signing up for an account. It really makes editing much easier. Best regards... -Ad Orientem (talk) 04:08, 18 January 2025 (UTC)[reply]
Good to see that the block no longer affects you. Dreamy Jazz talk to me | my contributions 09:18, 18 January 2025 (UTC)[reply]
Ad Orientem, zzuuzz, Dreamy Jazz, Drmies (and others) - I apologize for the delay responding to the ping for me here! I've been offline due to needing to take care of some potentially... very bad news that my doctor gave me last week. Let's just say it's not fun and I haven't told anyone about it yet. ;-) Reading the discussion, I came to the same conclusion that you all have already. It's either an autoblock, or it's a cookie block or caching block. If the user hasn't done so already, I'd be curious to see if clearing all browser data or using a different browser that they never typically use produces a different result. That's where I would start. If I'm needed further, please don't hesitate to ping me. :-) 23:10, 20 January 2025 (UTC)
Retrieved from "http://en.wiki.x.io/w/index.php?title=User_talk:82.4.73.190&oldid=1270725515"