User choice would be best indeed. The problem is that currently the votes are public but hidden from Lemmy regular users. Anonymize votes seems to be such a big problem the devs don’t even want to consider it.
I completely agree with the idea of more accountability. We are real people in acting public right here, we should be constantly aware that our actions have consequences. If you don’t want your pseudonym associated with a vote, don’t do it. It’s kinda like the opposite of 4chan, where instand of anonymous controversial content on top, here we have human-curated content being pushed up.
What it the instance signs the activity? Then it propagates to others instances after local validation. That way only local admins would have access to voting data. Malicious instances could still be defederated/blocked/have votes disregarded.
Can you name one that isn’t?
All federated data (thus public) should be easily available to the end user. Otherwise we create a false sense of security.
The jaguar and anaconda population would increase for a few generations, but it would balance it out after a while.
Why do you think feral chickens are a concern? Most chicken farms in Brazil are much farther from the Amazon, the deforestation land is mostly used to grow soy for animal feed.
I had success with iodine, it’s slow but it worked.
Fun fact: acrobatics are made with lower hydration dough.
If you want dough with crispy outside and soft inside you’re looking for a 65-70% hydration. Acrobatics with this will rip it apart. To open a higher hydration dough you use this technique: https://youtu.be/xzbW8CZx538
Sorry to burst your bubble, but there already exists a proposal to make communities work more like a cloud.
It’s just a matter of time before Lemmy and Kbin implement this.
Yes, the proposal is something like Nostr, but the clients can also relay data on request if they’re online. A little more decentralized.
Worth mentioning that the idea is not to make Lemmy abandon ActivityPub, but to allow further decentralisation.
There wouldn’t be a need to keep all data like a blockchain to query all data since most sort by hot/recent. Something like Gossipsub would suffice for most users.
But whenever an user queries for old or specific data, the request could be directed to a relay that archives and sorts all data.
Not a completely different protocol when the changes are additions to the existing one. The same protocol would still exist and be supported.
P2p enabled instances would have the option to reverse the communication flow, so besides the servers having to send updates to subscribed servers, the subscribers would have the option to ping peers/servers for updates.
This would help with sync issues when a post is made and the changes are not propagated to all subscribers.
Most people don’t come here to see archival stuff, so it wouldn’t be so bad if the p2p network cached ephemerally (time limit or a size limit). Old content could still be reached on servers designed to cache old stuff.
Events could be cached on the p2p network, so the phone only pings its peers for new content (mind the existing servers would be peers on the network).
You wouldn’t need to run the service 24/7, just whenever you’re using Lemmy and maybe a few minutes after so your interactions can propagate trough the p2p network. Also the existing servers could be used to cache and relay.
If you don’t want CloudFlare, it’s also possible to spin your own tunnel over DNS with iodine.
Hey, just curious: how would all the instances discover this type of fraud?
We already depend on trusting instances for a lot of what’s going on here, I don’t see why we shouldn’t be able to defederate untrusted ones.