User talk:2601:601:484:A0F0:191B:CC2B:6A48:F94E

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).

2601:601:484:A0F0:191B:CC2B:6A48:F94E (block log • active blocks • global blocks • contribs • deleted contribs • filter log • creation log • change block settings • unblock • checkuser (log))

---

Request reason:

Not only have I not committed vandalism, the allegedly blocked IP address differs from my actual IPv6 address

Decline reason:

The block is anon-only and does not prevent account creation. Create an account and you wont be affected by the block. Q ^{T C} 20:52, 29 June 2024 (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.

The Block Log Entry states that Ingenuity blocked 2601:601:400::/40.

1. At the time of writing this, my IPv6 address begins with 2601:601:484:: (Comcast). Unless I am missing something, I should not be affected by this block, but it appears that I am. If that is correct, something is coded incorrectly.

2. I try to be very precise with my language and sources (I am an attorney and an engineer) when an edit is based on facts. Other edits are simply correcting glaring errors in sentence structure, to correct poorly phrased language that can be misinterpreted, or for greater clarity. I explain the basis for any edits I make, and I cannot imagine any edit I have made would be properly flagged for vandalism. If there is a specific edit in question, I would be happy to review it and provide specific feedback. Assuming the edit is properly flagged, I would be stunned if it was an edit that I actually made. 2601:601:484:A0F0:191B:CC2B:6A48:F94E (talk) 20:46, 29 June 2024 (UTC)[reply]

2601:601:400::/40 covers 2601:601:400:: to 2601:601:4ff:: Q ^{T C} 20:52, 29 June 2024 (UTC)[reply]

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).

2601:601:484:A0F0:191B:CC2B:6A48:F94E (block log • active blocks • global blocks • contribs • deleted contribs • filter log • creation log • change block settings • unblock • checkuser (log))

---

Request reason:

Continuation of prior request2601:601:484:A0F0:191B:CC2B:6A48:F94E (talk)

Decline reason:

It is not permitted to edit via IP address(reading is okay, just not editing) because VPNs are used abusively by vandals. If you cannot access your original account, you may create a new one, which this block permits. Before you do, your VPN should be off and your browser cache cleared. You may also request an account via WP:ACC. 331dot (talk) 08:49, 30 June 2024 (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.

You recommended that I create an account; I already have an account. The reason that I was not logged in however was because it had been so long since I last logged in that I no longer remembered that password, and Wikipedia's "Forgot your password?" link is blocked for blocked IP addresses.

Note: I did try several IP addresses through the VPN that I use, which is Norton, but as a commonly available product, those IP addresses are also blocked.

My thanks in advance.

Please place new posts at the bottom for proper chronological flow, this may be easier to do if you click "edit" and not "reply". 331dot (talk) 08:49, 30 June 2024 (UTC)[reply]