I also prefer range or approval voting

Did you make a similar comment to OP, who only spoke negatively of a well-used and well-understood system?

What is OP’s proposed alternative? What’s a realistic plan to get there?

There is no voting system that fulfills all the Condorcet criteria; they all have some corner case

webdav? https://github.com/fstanis/awesome-webdav?tab=readme-ov-file

apparently, macOS and Windows still support this protocol

backticks for sure

Certain minimum knowledge is required if you don’t want to be low hanging fruit for criminal botnet operators who will use your system to launch attacks.

You can’t also beg/complain about tools “made for you” not existing - if they’re not already there, it may mean the problem can’t be reduced to appliance-user level.

If you’re building such a tool, why ask? Get uptake rate and user feedback data.

so edgy

pray, mr. anti, which is your party?

Clearly, it’s lost to both the Democrats and the carnival barker.

lol ok

that’s a ridiculous thing to say

if industrystandard and anticolonial are against me, I know I’m doing something right. Let’s get tokenboomer and givesomefucks and universalmonkey here too.

This guy wants you to throw your vote away.

The FCC has no mechanism to do so.

You haven’t lived until you’ve tried strawberry shrimp toast

it’s weird how often these same strawman arguments are the response when Rust’s safety advantage over C comes up. Usually the same adolescent tone too.

lol dude, I know what I’m talking about. I’ve been a software engineer for 30 years.

This is what a tryhard looks like, lol! You’re really twisting yourself around to “win” aren’t you?

Our team has reviewed this interaction, and cannot issue a refund at this time.

Also, get an Instant Pot. You can quickly make stock using pressure cooking, then can sauté onions/celery/garlic, then pressure cook dry beans without soaking (using your fresh stock), and then use the rice cooker mode to make perfect rice.

all while plugged into one unobtrusive extension cord running to your neighbor’s electrical outlet, to save money

While you’re spouting nonsense, this is happening:

https://www.infoq.com/news/2025/11/redis-vulnerability-redishell/

The vulnerability exploits a 13-year-old UAF memory corruption bug in Redis, allowing a post-auth attacker to send a crafted Lua script to escape the default Lua sandbox and execute arbitrary native code. This grants full host access, enabling data theft, wiping, encryption, resource hijacking, and lateral movement within cloud environments.

13 years. That’s how long it took to find a critical safety vulnerability in one of the most popular C open source codebases, Redis. This is software that was expertly written by some of the best engineers in the world and yet, mistakes can still happen! It’s just that in C a “mistake” can often mean a memory-safety bug that would put user data at risk (…) That’s the nature of memory-safety bugs in C: they can hide in plain sight.