Ahh, didn’t even know there was a flag for that. I don’t suppose you could link to the relevant w3c or FEP for it?
Ahh, didn’t even know there was a flag for that. I don’t suppose you could link to the relevant w3c or FEP for it?
All votes are public, they’re literally broadcast to the Fediverse writ large. You vote on something on your server, your server then tells the server owning the thing you voted on and that server then tells anyone who is interested (subscribers on other servers). That way everyone knows that this comment was voted on, but that information is indelibly tied to you - an entity on the Fediverse.
Lemmy devs just chose not to a) show that information in a UI (plenty of other software out there does) and b) not inform people that was the case. Which leads to the whole point of the thread, hiding this from users merely gives a false sense of security.
You say that, but you simply have to be using something that isn’t Lemmy and that information is there (doubly so if you’re an admin on any of these systems)
Except, if you’re using anything other than Lemmy at this point that information is already about. The Likes/Dislikes are considered public information by the protocol. Lemmy devs probably just didn’t get around to building out the UI for that before the Reddit APIcolypse.
All your followers would see it and sometimes you don’t want replies?
With a small amount of effort and the use of https://github.com/nanos/FediFetcher and https://github.com/g3rv4/GetMoarFediverse you can mitigate basically all those issues. It’s still not perfect by any means but it results in a perfectly usable single user instance.
The first populates the replies of the home timeline posts you see (as well as profiles of people it finds in those replies) and the second pulls down all the content from instances you select for your followed hashtags (choose mastodon.social and you can guarantee you’ll see most all posts with those tags)
IIRC your data would live on your chosen pod server - which does not have to be a fediverse instance.
I’ve not tried it but have been keep tabs.
The two main problems appear to still be ongoing PRs/issues; magazine/community sidebar content doesn’t update and doesn’t federate out at all to lemmy, and moderation actions don’t federate at all (any of the various types) - which is particularly problematic.
If only k/mbin federated better - I’d be all over it :(
If buying isn’t owning then piracy isn’t stealing.
You’ve not factored in egress costs. Which on Amazon can add up quite quickly.
“For example, if every time I post a new update on BlueSky, if I had to send my post to every single one of my followers’ repositories, that would be extremely inefficent”
Somewhat ironic to have this posted on and activitypub driven fediverse.
In nostr’s case, that’s tech bros and freedom of speech “absolutists”,
Don’t forget the crypto bros.
But, the theory goes, you’re not supposed to be reliant on third parties as you should be in control of your own domain (or within a few degrees of the person who is).
Large instances are what are antithetical to decentralisation.
Of course, the reality of it is that, it just hasn’t worked out like that.
Activitypub makes it next to impossible to “move” an instance to a new domain.
Every post/comment/and user is uniquely identified using the domain. In the eyes of ActivityPub changing the domain just makes each of those things a completely new thing.
You can set up a new service at your new domain and potentially get most all your users to migrate but they’ll be leaving behind their entire histories and as a “new” fediverse user they’ll only be discoverable via the historical posts for as long as the original server is reachable.
a lemmy instance can act as a censor and push the biases of their admins,
This is a strength of the federated model. In an ideal world instances are small and a user’s values align with those of their instance’s admins.
The problem here is that a single instance has grown so large that a decision like this has had such an impact.
There’s a lesson to be learned here: don’t push a massive update close to the holidays because, ya know, you might break federation and go on vacation for a week.
I mean, no one has forced any admins to deploy a new version. But yeah, this is an annoying one.
How about you assume less? I spent 40+ minutes looking for this here, here, here and here and I’m already fairly familiar having done work on two other ActivityPub based projects.
In addition public-addressing (or the lack of use thereof) in no way claims to achieve what you’ve stated - which is probably why it’s not the answer to my query.