Tossing a bunch of CCs on and assigning. :D

(In reply to comment #1)

Tossing a bunch of CCs on and assigning. :D

Do we want to do this concurrently with bug 18337?

mike.lifeguard+bugs wrote:

(In reply to comment #2)

(In reply to comment #1)

Tossing a bunch of CCs on and assigning. :D

Do we want to do this concurrently with bug 18337?

Yes, we do.

(In reply to comment #3)

(In reply to comment #2)

Do we want to do this concurrently with bug 18337?

Yes, we do.

Actually I was asking Brion :)

Please refine the configuration. Tor-blocked users can't edit any page at all (which includes their user talk page), so it is almost impossible to get yourself unblocked (other than through off-wiki methods) if you are within range of an exit node.

Ping Andrew -- what's the get-yourself-unblocked workflow look like? Do we need some on-wiki editing request or have we got someplace else we can clearly direct people to where their unblock request will get handled?

We can send people to unblock-en-l (a mailing listz). That seems like the most sensible thing to do for the moment.

mike.lifeguard+bugs wrote:

(In reply to comment #7)

We can send people to unblock-en-l (a mailing listz). That seems like the most
sensible thing to do for the moment.

Even if unblock-en-l were properly functioning, how does that help the other >700 wikis?

Looking for suggestions to improve the "get yourself unblocked" workflow.

Does anybody have any thoughts?

(Batch change)

These are low-priority miniprojects that I can mop up at some point when I'm doing general code work as opposed to working on a specific projects.

[Batch change]

Removing Dave McCabe from CC, who I somehow managed to add to the CC list of 12 bugs assigned to me.

mike.lifeguard+bugs wrote:

(In reply to comment #9)

Looking for suggestions to improve the "get yourself unblocked" workflow.

Does anybody have any thoughts?

Making a request on the user's talk page is fairly standard - that could be permitted for tor nodes. OTOH, the only problems we've had so far with TorBlock is when it doesn't block well enough, or doesn't block at all. I think we should go ahead and fix this problem already.

Is there anything else to action here?

It doesn't seem to be a shell bug... More policy, that is, even if something actually needs doing

Help?

Please reopen if there's anything else to still action here