---------- Forwarded message ---------- From: Andrew Garrett andrew@epstone.net Date: 2008/6/4 Subject: [Wikitech-l] TorBlock extension enabled To: Wikimedia developers wikitech-l@lists.wikimedia.org
Hi all,
After working through the code with Tim for a few hours this afternoon, the TorBlock extension has been enabled on Wikimedia.
The TorBlock extension will override local IP blocks to provide a consistent treatment of tor. Currently, this involves allowing only logged-in users to edit, and requiring tor users to have 100 edits, and a 90-day-old account, prior to being autoconfirmed.
Hopefully, this will provide a balance between allowing users to edit through tor without the difficult process of granting per-wiki IP block exemptions, and preventing pagemove vandals (such as the user known as 'Grawp' on English) from using Tor for vandalism and so on.
I haven't yet implemented this, but I am interested in the prospect of marking Tor users as such on either CheckUser, or (privacy policy depending) on Recent Changes.
-- Andrew Garrett
_______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On 6/4/08, David Gerard dgerard@gmail.com wrote:
---------- Forwarded message ---------- From: Andrew Garrett andrew@epstone.net Date: 2008/6/4 Subject: [Wikitech-l] TorBlock extension enabled To: Wikimedia developers wikitech-l@lists.wikimedia.org
Hi all,
After working through the code with Tim for a few hours this afternoon, the TorBlock extension has been enabled on Wikimedia.
The TorBlock extension will override local IP blocks to provide a consistent treatment of tor. Currently, this involves allowing only logged-in users to edit, and requiring tor users to have 100 edits, and a 90-day-old account, prior to being autoconfirmed.
Hopefully, this will provide a balance between allowing users to edit through tor without the difficult process of granting per-wiki IP block exemptions, and preventing pagemove vandals (such as the user known as 'Grawp' on English) from using Tor for vandalism and so on.
I haven't yet implemented this, but I am interested in the prospect of marking Tor users as such on either CheckUser, or (privacy policy depending) on Recent Changes.
-- Andrew Garrett
This is certainly interesting, but I cannot seem to find any documentation on how exactly this would 'work'. Is it opt-in? Do admins have to do something?
For example, today I re-enabled Tor and I tried creating a redirect. I was blocked with the normal Tor block pages regardless of whether I was going through secure.wikimedia.org or en; my account has been around for hundreds of days, has like 30k edits, rollback & move privileges and so on, so if I am understanding this right, I should've been able to create the page just fine. But I couldn't, so I didn't.
-- gwern
On Thu, Jun 5, 2008 at 8:29 PM, Gwern Branwen gwern0@gmail.com wrote:
For example, today I re-enabled Tor and I tried creating a redirect. I was blocked with the normal Tor block pages regardless of whether I was going through secure.wikimedia.org or en; my account has been around for hundreds of days, has like 30k edits, rollback & move privileges and so on, so if I am understanding this right, I should've been able to create the page just fine.
Check Tim Starling's post to this thread, about 22 hours before yours. The functionality of overriding hard blocks has been disabled pending further discussion. The extension still (if I understand correctly) puts a soft block on any exits that haven't been manually blocked, but does nothing else at the moment.
On Fri, Jun 6, 2008 at 8:58 AM, Simetrical Simetrical+wikilist@gmail.com wrote:
On Thu, Jun 5, 2008 at 8:29 PM, Gwern Branwen gwern0@gmail.com wrote:
For example, today I re-enabled Tor and I tried creating a redirect. I was blocked with the normal Tor block pages regardless of whether I was going through secure.wikimedia.org or en; my account has been around for hundreds of days, has like 30k edits, rollback & move privileges and so on, so if I am understanding this right, I should've been able to create the page just fine.
Check Tim Starling's post to this thread, about 22 hours before yours. The functionality of overriding hard blocks has been disabled pending further discussion. The extension still (if I understand correctly) puts a soft block on any exits that haven't been manually blocked, but does nothing else at the moment.
http://lists.wikimedia.org/pipermail/wikitech-l/2008-June/038183.html for those of us who do not subscribe to wikitech-l.
-- gwern