I’ve been on Lemmy for some time now and it’s time for me to finally understand how Federation works. I have general idea and I have accounts on three federated instances, but I need some details.
Let Alpha, Beta, Gamma and Delta be four federated instances. I have an account on Alpha and create a post in a community on Beta. A persoson from Gamma comments on it and a person from Delta upvotes the post and the comment.
The question: On which instances are the post, the comment and the upvotes stored?
You must log in or # to comment.
Federated content is stored in the balls.
Thank god someone made the joke already!
I wouldn’t have had the federated content holdersMy balls?
Everyone’s balls
Only Ligma’s.
Poor Ligma. Worst case of Dee’s syndrome I’ve ever seen.
It’s decentralized, so across everyone’s balls
I can confirm this to be true
As already noted, on all of them.
The easy way to grasp how it works:
When you, on instance.alpha, view a community on instance.beta, you aren’t actually on [email protected]. You’re actually on an entirely separate copy - [email protected]@instance.alpha. That’s the community you’re reading and posting to and upvoting/downvoting in. Meanwhile, people on other instances are each on their own locally hosted copies of the same community.
The lemmy software (or kbin or mastodon or whatever) then periodically syncs up all the local copies of [email protected], so you all end up looking at (more or less) the same content, even though it’s actually a bunch of technically separate communities.
deleted by creator
It’s less efficient than a centralized forum would be, but efficiency isn’t the only or even the highest priority. Decentralization is the explicit point of the fediverse, and to the degree that that requires sacrificing some measure of efficiency, that’s just the way it goes.
The goal was to build a system that would be robust and relatively seamless while remaining decentralized. That’s more or less what they’ve done. There’s a fair amount of fine tuning and tweaking left to be done, and actively being done, but the basic system is what it is because it best balances all of the goals.
Also, all data isn’t stored on every Lemmy I stance, only (or mostly I guess) where it is relevant.
As long as 1 person from an instance is subscribed to a community, that person’s instance will fetch everything that happens inside that community (and keep storing it even if they later unsubscribe, unless manually purged by an instance admin)
So not everything everywhere but quite not that efficient …
Thanks for the explanation.
Right, which on a side note is most of why I have accounts on a number of different instances and regularly switch between them - because each instance is at least subtly different, since they each have different userbases, and thus somewhat different sets of subscribed and thus federated communities.
But if you on instance.alpha subscribe to a community on instance.beta that would federate the community to your local instance, right? Is there something I’m missing?
Right, but of course if you don’t subscribe to it (and nobody else does) then it doesn’t.
So, for instance, if you go in through an account on a narrowly specialized instance, you’re potentially not going to see a lot of the communities from other instances at all, even on their All, just because nobody’s bothered to subscribe to them. And you’ll likely see highly specialized communities that fit well with that instance that you might not see anywhere else.
The smaller the instance is, the more likely that is.
I have accounts on a couple of small instances on which I haven’t even bothered to subscribe to anything, since their All already matches what I want frim the instsnce.
Yes, if you know about that community. However, by browsing the all feeds of multiple instances, you come across communities you weren’t aware of and can subscribe to on any of the instances you have an account on. Assuming, of course, they all federate.
that’s possibly the best explanation of the difference between a corporate social or other media and a decentralised open source one.
It depends what you mean by inefficient. It’s very efficient if you’re optimizing for robustness and control of data.
It’s also very efficient if you’re optimizing for having an actual fucking conversation without algorithms or ads.
We’ve been trying to reach you about your cars extended warranty…
Control or redundancy of data?
If there is a federated delete, I get the impression there is no actual way to ensure that data is deleted?
I don’t mean control from the perspective of someone posting data. I mean from the perspective of the server owner.
Sorry, what do you mean?
Pretty good answer but there’s no periodic sync. From the moment a community is subscribed to, the instance that is home to the community will send all activities in that community to the subscribed instances as they happen.
That’s why you don’t see old content all being synced. Just new content (and some old content if it is liked or replied to after subscribed)
Is there a single source of truth? It really sounds like split brain is possible?
All instances may have their own copy but I imagine the community the instance was posted on is important and need to be up?
Well, the answer is “it depends”
For the community as a whole, I would say that the instance that hosts the community must be up to federate any new posts to other instances. Because it works a bit like:
Instance A hosts Community 01.
Instance B user posts to Community 01.
Instance B federates the post to Instance A
Instance A federates the post to Instances C, and D.So, if instance A is down, the post will exist only on instance B.
But, federating the posts and comments themselves is not the only way an instance will get posts and comments. Consider the following situation. The post above exists on instances A-D. But after it is posted, Instance E subscribes to the community. Instance E will not have the above post. They will only start getting new federation events.
However, say for example someone on instance C likes the post? The like event will be sent to Instance E. Instance E will see the like, try to find the post (the post/comment URL is included in the like event) and fail. So, it will then look up the original post. Here’s where it gets interesting. That URL will not be on Instance A where the community lives, but on Instance B where it was posted. So, in this case, if Instance B is down, Instance E will not be able to fetch the post.
However, if all the instances are up, Instance E will get the post add the like and add to database. This is why when subscribing to instances you will get some old content appear but not all. Because if the old content is interacted with, it will be fetched to render the interactions.
This understanding is based on my understanding of kbin federation. But, I would be very surprised if lemmy did not work the same.
EDIT:
To be clear, to see what already is federated no other instances except the one you’re visiting need to be up. For federation of live events happening to a community, the instance hosting the community must be up and to fetch content needed for a federation event (for which the referenced object was not received via federation), the instance the content was created must be up.
Very well written! Seems easy enough, thank you!
It’s stored on all 4.
Regardless of which on you create the content on, assuming they all federated with each other correctly, every instance hosts its own copy of your posts.
So, data is not normalized. Isn’t it a waste of storage? Same data on all instances.
It isn’t a waste if it provides redundancy and prevents one server from being in control of all data.
What do you mean by “normalized?”
I see your point.
I used the term “normalized” in the context of databases. One piece of data should exists only once. But, this contradicts your points of redundancy and control.
That isn’t what normalized means in the context of databases.
Also databases store the same data many times over often. For redundancy and load-balancing purposes. Really, federation just takes care of replication somewhat.
That’s not what “normalized” normalisation means in the context of databases.
Ok, I come from the signal processing world where that means something very different.
The only objection I have with that is redundancy is useless because if the main server who “host” the community goes down then all the other copies will die too as content can’t be added anymore.
There’s no mechanic for orphan communities
It’s mostly intended for caching content to speed up load times afaik
All of them. If you can see it from an instance, it’s stored in that instance.
The only exception are images which may or may not be stored depending on the exact backend software and configuration.
Both “alpha” and “beta” has authority to hide the post (one hosts your account and the other hosts the community) from the rest of the federation. Similarly, both “beta” and “gamma” have the authority to hide the comment from the federation. That said, instances can also individually hide/purge stuff from their own views without affecting the wider federation if they so choose (which is how things like .world’s blocking of piracy communities work)
“beta” handles distribution/“boosting” (in masto speak) of the post and comment to other instances (however “gamma” will send it to both “alpha” and “beta” as it’s a reply to “alpha”). AFAIK “alpha” and “gamma” handle the boosting of the upvotes they receive from “delta” (though I could be wrong on that part).
Oh, and “boosting” doesn’t mean “i got 1 new upvote on this comment :3” it means “delta has sent me this exact Like event owned by person@delta associated to comment@gamma (and a lot of other data)”. There are also keys and signatures involved to make things a bit harder to spoof.
Nice try, Spez! Get outta here! Go on, get!
Both. The text data is in the database of all instances that are federated. Your account credentials are only stored on the instance you’re registered to.
On all instances. Each instance has copy of what happened and every action is relayed by community instance (in this case, Beta) to all subscriber of the community.
So if I make an instance, I can scrape all the content and gather data on every user and sell it to Cambridge analytica?
Technically, yes. But if you are caught red handed, be ready for the mass ban to your account/instance.
But if it’s just sat there silently data gathering, nobody would know?
Yup, that is what professional/corporate scrapper do from the very beginning. Fediverse has poor privacy, and it is designet that way. It is better to share only safe content to fediverse for our safety, and share more private things on messaging/chatting apps like matrix or email only to person we trust.
What info do you think they will get? The only info is what you put in the public info on the user profile on your instance. So they can get your username (well user@instance), avatar, about info. That’s about it. Anything else like email address and password hashes are only stored on the instance you signed up to.
Every single comment and post anyone ever names and anything they are subscribed to. Run everyone’s content through some sentiment analysis, and now you have a great set of users, emails and their commonly used IP, grouped into interests, general mood, and political leanings, perfect for advertising.
Where are you getting email and ip from?
your votes are visible to all instances. it’s easier to think about when you think of voting like favoriting in mastodon except lemmy doesn’t send a notification
Yes, I discussed this in another thread. There could be ways to protect this info. But, it would mean totally changing (and agreeing with all other threadiverse apps) the way this is handled. Even then, I’m not sure you could prevent exploitation if the full info isn’t sent. On kbin this info is visible anyway. You don’t need any fake instance to do it.
What’s my name?
deleted by creator
