Hacker News new | ask | show | jobs
by xoa 1526 days ago
Stupid and disappointing. Wikipedia and others should move decisively away from using IP addresses as any form of unique ID and address the actual problem in a way that still preserves the option for useful pseudonymity and participation. The basic issue with moderation is the balance between the time/resource cost of moderation and the time/resource cost of evading it times the quantity of bad actor interest. Like if it costs the site two cumulative human minutes and paying for that somehow ($2 at $60/hour, or limited volunteer resources that should still be valued) to make a moderation decision but bad actors can evade in seconds for free then the site will eventually suffer from resource exhaustion if there is enough attacker interest. Conversely if it the cost on the site side is two minutes/$2 but hours/$10+ on the attacker side the site is going to win. At some level of imbalance even the best funded attacker will run out first. IP addresses have been used as an extremely clumsy and increasingly bad proxy for cost, because it takes some level of effort/time/expertise to evade it. But as well as evasion being automatable and growing worse (hard to see how IPv6 won't be the final nail in the coffin there at long last) the side effects against innocent and important usage are very bad too. Some sites use money as a proxy (SomethingAwful's (in)famous 10bux say) and that can work in some niche cases, but is also less than ideal for anything that aspires to be global and widely inclusive given gross inequalities in income. It's impossible in most cases to set a level that isn't simultaneously a blocker for many while not even being a speedbump for others.

Instead it's way past time they just attacked the problem directly with some flavor of more formalized cryptographic representation of time. Like just give new users a number to do prime factorization on tuned to a desired target, then sign the result. Ensure they need to do a few hours/days/whatever of crunching (could be graduated, a few hours gets you initial editing rights then you're expected to crunch a bit more over the following months to reach full user level). Scale over time with increasing processing power. Near zero cost to verify. Now even with hacked routers and so on it still always takes some time. For people who don't get banned it's a one-time cost, no problem, amortized over years/decades (Wikipedia is 21 years old now, and there are other older forums still around too). Anyone in the world can participate no money required, just a computer. But for attackers it's a constant burn. And it changes to calculations for things like soft bans too. If you've got a token representing a week's worth of compute built up over a few years and get a 48 hour ban, the incentive against ban evasion is high. It's not possible to build back up another token before the ban expires.

It's a shame there isn't some standard for this, no reason in principle a handful of authorities couldn't make chrono-tokens that any site could recognize and keep their own DB of. No permanent identity involved, no law enforcement, always the chance to start fresh, every site can choose whether to worry about other sites' bans or not (or contribute back their own or not). A token need not be tied to any account at all in fact. And no algorithms involved either, humans can take the driver's seat again because the cost equation is firmly back in moderators' favor and they have a dynamic tool to respond to abuse (they can just temporarily increase the time req during an attack surge as high as needed to quench it while not hurting long time users or even stopping new ones from signing up then lower it smoothly back down to let new people start faster as whatever caused the attack winds down).

It stinks we're into the 2020s and moderation doesn't really seem much different than the 90s.

5 comments

Using hashcash and other proof-of-work schemes to limit spam and similar abuse sounds appealing, but I don't see how you can make it work in practice.

1. Defenders use standard PCs and mobile phones. Attackers use GPUs, FPGAs and ASIC and run them in places where electricity is cheap.

For traditional hash algorithms this gives the attacker a thousandfold or so advantage. There has been some work on closing the gap in the context of crypto currencies, but I don't know how close they got.

2. It takes a phone (or even a PC) a long time to burn through $2.

3. Attackers have large botnets and don't pay for the electricity consumed by these.

These ideas always fall short for various reasons in practice. One is that you mainly punish honest users who have to install and run this PoW crapware just to make a small but legit edit. Wait, I have to lock up my CPU for how long to fix a typo I stumbled upon? Lol, forget it then.

Meanwhile, abusers just farm PoW solutions and make it negligible. You end up with a solution that’s even easier to farm than quick expiry captcha.

And your idea doesn’t stop you from having to implement moderation anyways. You have to do the same work.

When making a response it helps to actually read the comment and engage in good faith.

>One is that you mainly punish honest users who have to install and run this PoW crapware just to make a small but legit edit.

I covered this. It's trivial in such a system to still have no-cost be the default, and ramp up only for certain criteria or during hot spells. Which is what I wrote. Also, an RSA cracker can run fine as javascript, no need to install anything. And legitimate users can build up over long periods. Further, how do IP bans, the existing default, line up with your "honest users" thing hmmmmm? You did at least read the title of this comment section right? You are aware that this is all in the context of something that is also a broad sledgehammer right?

>And your idea doesn’t stop you from having to implement moderation anyways.

I never suggested it did? Quite the contrary? Hello?

>You have to do the same work.

No, you don't have to the same work if attackers cannot attack as quickly and cheaply. Duh.

> address the actual problem in a way that still preserves the option for useful pseudonymity and participation

You mean like supporting use of pseudonymous accounts that don't require more than an email to register, just like HN? Wikipedia already does this. It's trivial to sign up with a throwaway email account. No one cares unless you try to abuse or game editing by making sockpuppets to sway debates.

They're also exploring how to mask IPs. https://meta.wikimedia.org/wiki/IP_Editing:_Privacy_Enhancem...

>It's not possible to build back up another token before the ban expires.

I think you fail to realize how slow low end devices that can use wikipedia is compared to the latest high performance processors.

> Wikipedia and others should move decisively away from using IP addresses as any form of unique ID

I think they're already there.

> Proxy blocks are not targeted at individuals

There are italics on the original page.