I somewhat recently ran across VanillaOS, which I have only really had time to install and play around with for a few minutes, but it seems really cool. A very brief overview is that it is a sort-of-but-not-really immutable OS that leans very heavily on containerization to allow you to install packages from any other distro in a seamless-to-the-user way. So you can install an application (cli or GUI) from an ubuntu repo and use it along side an application from an arch repo. It's ubuntu-based, but according to the info on that link, the next release switches to being debian-based.
I mostly use ChromeOS these days-- well, I guess technically I mostly use SteamOS these days-- so I don't have a lot of hands-on experience with VanillaOS, but I found the concept really cool and from a few minutes of playing around with it, it seemed to work pretty well with respect to the containerization stuff.
Steam released an entire Linux OS; I think it's safe to say that Steam is on-board with Linux gaming in general. Everything has bugs. If you're just looking for a reason to justify piracy, then fine, but this seems a little out there. What will you do if Lutris releases with a bug that crashes your system? Switch to Windows? haha
Well yes. They can still be made more or less easily accessible.
Only on a server by server basis. The data is being transmitted and received. If a server decides to hide that info, that doesn't necessarily mean that other ActivityPub compatible services will also hide it, let alone services running the same software.
You just need to get used to the idea that a vote is as much a pubic statement as a comment, and act accordingly.
I feel like people read a comment that linked XMPP with EEE and keep parroting it while not understanding it.
XMPP still exists, but people largely don't want "Instant Messaging" anymore. They don't want to care about whether the person is online before they can send a message.
Google dropping support for XMPP didn't do that, it's what caused them to drop it. They moved on to what people wanted: asynchronous messaging.
This concern about the now overused "EEE" stuff is blown away out of proportion.
You can't hand wave away the technical limitations like that. If you want downvotes, and you appear to want them, and you want to be on a federated system, and it appears you do, then the federation will require linking downvotes to users.
Downvotes aren't an outwardly anonymous way to show disagreement like they were used on Reddit. They're like a comment of disagreement. If someone harasses you for downvotes, report them. And block them. Just as you would if they did so for a comment you left.
I like that voting is public because it makes voting (up or down) a public statement. If I look at a person's voting history and see upvotes on racist comments and downvotes of well thought out comments I can know with some certainty that I can disregard the opinions of that person. Further, it might make people more thoughtful about what they vote on.
Have you stopped to think about how that works in practice? If I downvote something on kbin (where I am now) and it federates to feddit.nu, how does that work without also knowing my username? As I think I already saw someone point out to you, stripping out that information would make it very easy to send unlimited downvotes to any given instance, because it would just be a counter of downvotes without a user associated with it.
The only reason downvotes were "anonymous" on reddit was because it was closed source and didn't federate that information to other services. The downvote was still linked to your account, just obscured; Reddit admins could certainly see what you downvoted. This tactic won't work on any platform that uses ActivityPub, or something similar, without getting rid of downvotes entirely. It's probably best you get accustomed to this; treat it as you would a comment that says "I think people should see less of this" or something equivalent.
My question was more along the lines of "why do you need to label any given reason as a 'primary' argument". You've already been given counter-points.
I think that if you're concerned about this, you should seek out an instance that both does not federate downvotes and does not display the downvote button. Then you will be unable to downvote, and you won't see any downvotes from other instances.
To what end? So it can get converted into a real currency immediately? I understand (since you spammed it everywhere) that you can donate via crypto, but that's only because crypto can be converted into a real currency.
Give it up, my friend; fetch isn't going to happen.
crypto is the beanie babies for this generation. Some people are going to make a lot of money but a vast, vast majority are going to be the proud owners of something worthless that they spent a lot of money on.
I didn't mind the reddit version when there was only one award and it granted the awardee premium benefits for a month. I felt like that was a good balance. Not that I think lemmy needs that kind of system-- at least not yet.
Trolls know why they're being downvoted; for reasons I don't understand, they seem to enjoy it.
You probably shouldn't be downvoting people having a good-faith discussion, but if you do, the venn diagram of people having a good-faith discussion and unstable enough to harass someone for downvoting them is probably pretty small. Small enough for the block function to mitigate it.
Flip it around. Anonymous downvotes would let anyone spin up a lemmy instance, fill it with sockpuppet accounts, and downvote everything by hundreds or thousands of downvotes, and it would be impossible for users to know the difference.
I somewhat recently ran across VanillaOS, which I have only really had time to install and play around with for a few minutes, but it seems really cool. A very brief overview is that it is a sort-of-but-not-really immutable OS that leans very heavily on containerization to allow you to install packages from any other distro in a seamless-to-the-user way. So you can install an application (cli or GUI) from an ubuntu repo and use it along side an application from an arch repo. It's ubuntu-based, but according to the info on that link, the next release switches to being debian-based.
I mostly use ChromeOS these days-- well, I guess technically I mostly use SteamOS these days-- so I don't have a lot of hands-on experience with VanillaOS, but I found the concept really cool and from a few minutes of playing around with it, it seemed to work pretty well with respect to the containerization stuff.