814
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 18 Aug 2024
814 points (97.9% liked)
Fediverse
28468 readers
187 users here now
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy
founded 2 years ago
MODERATORS
Yes. That's what I said. I'm actually not 100% sure about it; for all I know there's some way to get it, but AFAIK all the existing softwares don't publish votes "after the fact", only at the time to current subscribers. But then, of course, it's kind of a moot point because you can just grab it from any mbin instance's DB through the UI without needing to do anything special or any particular knowledge.
Not really. You can have your client talking to all the servers and grabbing votes for whatever you're subscribed to, and losing votes for anything you're not subscribed to. It works basically exactly that way for one-user instances already.
Tru dat. 100% agreed. It seems like there are all these people in this thread arguing that their votes need to be private. Their votes are not private, and will never be private, for as long as ActivityPub is what they're using. I can see some value, maybe, to making it slightly difficult to extract the information instead of just giving it for free to everyone, but holding onto the idea of your votes being private is a gateway to unhappiness and only unhappiness.
It works like that for servers because servers are assumed to have high uptime, so (in theory) push-based communication should be enough. However, we see that this is not true even for servers (e.g, medium-sized instances getting out of sync with LW because they can not keep up with all the data being sent to them) and this will be specially true in the case of a network with tens/hundreds of thousands of separate clients. No server will be willing to push activities to all those inboxes, so we will need to have some pull-based form of communication as well.
Oh, yeah, at that point it'll be a scalability clusterfuck. No idea what the solution is. Maybe something with persistent caches run by third parties or something? That actually would be fine, since all the actions are signed with the private key of the actor, I think.
ActivityPub is not to me a real great designed protocol but it's whatever. Usually the key part for social networks is the "social" part of it; the protocol or the web site can be pure shite and if people like interacting with the other people there then it's fine. But yes, you are correct that beyond a certain point of scalability there are some dragons lurking that don't have obvious weak spots.
The problem is not with ActivityPub, but the implementations. No one ever claimed that it should be only a push-based system, but it seems that everyone working on AP software can only think in terms of server-to-server interactions to get the data and then reinvent the wheel by developing their ad-hoc API.
AP is fine if we treat it as a messaging protocol and use it to power offline-first applications. The devices do not need to have all the network's data, just the one that the user has actively interacted with.