cypherpunks can still post comments and edit old ones.
i disabled the cypherpunks account until we can get a hold of this.
thank you for taking care of this abuse. sad to see this is needed. but best choice atm.
(excuse me, don't get tricked by my account name, I'm kind user. i created this because my comments was edited)
looks like cleaned offensive content cleared.
still there are a lot of changes of comments and trac wiki pages in past over weeks with interval increasing.
as the account now got disabled, i cannot log into it and revert this. where or how to report? there is something around 100 comments affected 5 pages.
shall i list them in a new ticket or here? would someone revert this things? wiki page hard to revert because trac detect spam (limit exceeded) if try to do so. comment only can revert by account of commenter and since account disabled, this not possible.
Ok. Pages can get reverted by track history without loosing formatting. But take long time because of link limit can only revert 2 lines per page edit.
Comments can't restore but quote versions of track diff history. You find comment history link underevery comment below the link DIFF last edited ago.... if there was multilple edits you can go back in time by selecting previous.
If restore through quotes. Order of conversation. Get lost.
At least nothing really lost. Just hidden by first look.
What's wrong with this anti-Cloudflare lunatic? Did he know that Tor's threat model has no problem in defying it? We all know Cloudflare is bad can you all stop now?
Not all. As far as I can see from this ticket #24351, there's some people who don't understand Cloudflare is bad. I really don't care whether they dislike anti-Cloudflare activity or not.
Whatevs. I'm sorry if #24351 or GCW hurts your feeling. Just don't replace any documents to some illegal images, ok?
There was still someone vandalizing the wiki. So we disabled several cypherpunks accounts and online assigning viewing permissions to authenticated users.
Out current solution is that people should ask for more permissions like #34210 (moved). After some time we will probably reset this policy, but experience from similar cases suggests that it needs some cooling down.
I tried to use several regexes to disallow non-alphanumeric characters, but even simple ones like [AB] didn't work as expected (only allowed A and B plus non-ASCII characters). Also (?a)[AB] and similar combinations didn't work. Currently it is unclear how to make this work. We'll investigate later and adjust the settings if there is a good fix. For now I'll close this ticket.
Trac: Status: assigned to closed Resolution: N/Ato fixed