this post was submitted on 15 Sep 2025
336 points (98.0% liked)
sh.itjust.works Main Community
8240 readers
555 users here now
Home of the sh.itjust.works instance.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
My point is that if a U user is on L local instances and R remote instance gets the vote, how does R know if U is double spending or not?
Hash the whole fucking thing and store it with the entity being voted on.
UserID, UserServerID, EntityID, EntityServerID all together hashed.
Mind you, I'm assuming those pieces of information exist because thingID + thingServerID makes sense as a way to identify "thing" (user, comment, post) in a federated system.
Server is the server that hosts "thing": the server where the user is registered, or the server hosting the forum where a post was made or a comment was made under a post.
On an incoming vote, server calculates the hash. If the same hash is already present, server doesn't accept another vote if it's the same way or changes the existing vote if the new one is different.
Mind you, this is all blue sky thinking based on how I myself would design such a system as I can't be arsed to go learn Lemmy's API and data model just for this.
In your model Remote server would still know about User's votes, which is what we have now with lemmy.
So in the data-model the votes are linked to the User rather than to the entity being voted on?
I supposed it makes sense considering that the user him/herself does get displayed in a prominent way where they voted and how.
I hadn't considered that side of the data flows :/
I see, guess I underestimated the problem a bit, I have to think about it some more.