Redis, rabbitmq. There are infrastructure where all nodes work but only one node is responsible for properly and timely synchronizing changes, which is a hard problem to solve in a distributed fashion.
It has similarities though, as pointed out in orher comments. For one, a user might be more careful with downvotes if they are afraid of negative consequences e.g. harassment. With piblic votes, there would therefore be a bias towards upvotes and and people abstaining from downvotes, i.e. less interaction in total.
Downvotes serve a purpose today, letting us quickly scan which comments are controversial or even harmful to the conversation. I, for one, usually sort most threads by votes and then skip the comments with many downvotes but for controversial topics, I instead seek out the comments that have both many upvotes and downvotes.
These would be harder to find given the above bias.
They don't require it, you can also go to a physical office if you don't have BankID. Also BankID is a private company wo is problematic on several levels.
Many government agencies have started accepting multiple ways to identify yourself such as Freja.
Yes but I find all this both racist and sexist. Not all men in India are creeps, even if may be a rampant problem. Shouldn't they instead try to punish the weirdos?
The market would open wide for filling aeevices, where you bring your own reusable bottle. Also, water should be free and not put in bottles at all.
It's unfair to blame capitalism when the state obviously failed (even if through lobbying) to deliver clean water. Other countries have no such problems. Water is basically free where I live.
We have huge taxes on single use bags, and more taxes are coming.
I totally agree with you. I'm not sure that strategy works though. All they will (still) see is 0% linux/firefox users no matter if we spoof or not. It will just be fewer users.
It's actually the company's problem. They usually opt to add more debt though, rather that wade through the old stuff.
In the end, all software sucks and should be replaced as soon as possible. Code quality is a lie we tell ourselves so that we can sometimes be proud of our work. It's usually the code we are most proud of that is the worst. Design patterns everywhere making the vode overly convoluted and "future proof". The only future proofing that happens is that no-one will understand it, so they won't change it. Trying to design for the future usually makes it harder in the future.
Username checks out though