Open main menu

The stars baked my bones,
The oceans culled my blood,
And the forests shaped my lungs.
Who am I?
‹‹‹ A. A. Attanasio | in | Radix


We reject kings, presidents and voting.
We believe in rough consensus and running code.
David Clark ›››
Earth Eclipses Sun-ap12-s80-37406.jpg
Blue2F8CC2 circle 100%.svg
talk
Blue circle logo.svg
email
Urantia three-concentric-blue-circles-on-white symbol.svg
home
Blue circle logo.svg
edits
Blue2F8CC2 circle 100%.svg
info
‹‹‹ archive
01 | 02 | 03 | 04 | 05 | 06

Contents

Special:AbuseFilter/133Edit

Easiest way to protect your archives from the malicious is to add it to one of the archive protection filters.  — billinghurst sDrewth 12:48, 7 January 2019 (UTC)

@Billinghurst: Thanks for the tip. RadiX 14:00, 7 January 2019 (UTC)

Tech News: 2019-02Edit

18:30, 7 January 2019 (UTC)

ROXELANA22 LTA is backEdit

Lock all:

181.49.88.0/21 xwiki-contribs xwiki-date ST IP info WHOIS robtexgblockglistabuselogipchecker - Current IP range; has already been Globally Rangeblocked twice

@RadiX, Green Giant, and Ajraddatz: Hello. It's been a while. The severe LTA User:ROXELANA22 has returned, 1 month after the expiration of his 6-month Global IP Rangeblock (and 1 month after creating a string of new sleeper accounts). Just recently, this LTA went a mass vandalism spree across multiple Wikimedia Project sites, as he has done in the past. He also attacked me and other users on Commons and Meta. Can someone please run a sleeper check on his accounts, Globally Lock all of the accounts, and also Globally Rangeblock his IPs for another 6-12 months? Global IP Rangeblocks appear to be the only effective solution against his cross-wiki vandalism and trolling, and his listed IP range above has already been Globally Rangeblocked twice for persistent cross-wiki abuse. You can see this discussion for more information on the severity of his abuse, and why Global Rangeblocks are necessary, in case anyone forgot. In short, this LTA uses a dynamic IP range, and he will continue to create masses of cross-wiki sock accounts for vandalism, trolling, and degrading personal attacks (such as this one), unless he is unable to use his IPs. Thank you. (PS, the 6-month Global Rangeblock enacted last June appeared to have been 100% effective at stopping his cross-wiki vandalism and socking.) LightandDark2000 🌀 (talk) 04:23, 14 January 2019 (UTC)

  Done although I'm not confident about reinstating the globalblock as it seems to have significant collateral damage on the IP range. RadiX 17:15, 14 January 2019 (UTC)
@RadiX: How about an anon-only Global Rangeblock? That setting would allow other legitimate users on that range to continue editing. As for the anon IPs, I'm afraid that they need to contact a Steward to have an account created (or login to their own accounts) to continue editing, because the cross-wiki abuse from this LTA is extremely severe and has been continuing for more than 10 years now. The Steward contact message can be included in the block notice, as done in the past. The Dog and rapper vandal is another LTA with an extensive history of abuse, and yet, the local and Global rangeblocks enacted for this vandal has much more collateral damage than any of the blocked ever used for ROXELANA (especially the 2 Global Rangeblocks for the DRV LTA in May 2018), but they were implemented anyway because of the extensive abuse by the vandal. Given that ROXELANA has already gone cross-wiki again (as seen in the account logs for DDIIAANN), can you please implement a 6-12 month "anon-only" block on the range? Otherwise, he's going to return again soon, and his vandalism will worsen in severity and frequency, as they did last year. This link indicates that he has been using the same IP range for almost 3 years now. Thanks. LightandDark2000 🌀 (talk) 18:05, 14 January 2019 (UTC)
I'll have a look into this. RadiX 19:36, 14 January 2019 (UTC)

Tech News: 2019-03Edit

Return to the user page of "RadiX".