

God, this video makes me feel old. The fact that folks can be confused about how a federated service works boggles my mind. I mean, I get it. Walled gardens have been the default for 20 years now. But still.
God, this video makes me feel old. The fact that folks can be confused about how a federated service works boggles my mind. I mean, I get it. Walled gardens have been the default for 20 years now. But still.
Might take a look at the instance I’m on. Lemmy.sdf.org. It’s pretty chill, and SDF has been doing the social media thing since the 80’s without much issue. Started as a dial up BBS devoted to anime back in the day. Leans anime, music/art generally and computers. Supported via donations.
Sounds like a solid plan.
Unless you already have a RPi available for use, I would consider basing around x86 hardware. Nothing wrong with the Raspberry Pi’s, it’s just if you need to buy hardware, there’s much more powerful computers available for similar price points. Won’t be as simple or straightforward nor as energy efficient, but if you start adding additional services, you’ll be glad for the extra RAM and processor performance that is available.
So this is my third go at replying. First attempt was damn near collage level. Second attempt found me rewriting the Internet for Dummies book that originally taught me about how the internet works when I was 10. Seriously, if you can find a copy of that particular edition, give it a read. It’s the third edition from 1995. You may need help from !piracy@lemmy.dbzer0.com to find it though.
Honestly, the Fediverse has the same problem that the internet itself has. That is that it is far easier to just use than it is to explain what it is but the fediverse and the internet itself work almost exactly the same way, at least at the user level.
I’m going to completely ignore everything under the hood for the sake of simplicity. Additionally I’m going to over simplify to the point of inaccuracy, because it gets really complicated really quickly once you scratch the surface.
Imagine a spider web. Each point where the web interconnects is a server. Each server on that web can communicate with every other server on that web (don’t ask how, that’s part of the bit we are ignoring).
Now each fediverse service is kinda on its own web. Lemmy is on one web, Mastodon is on another, Pixelfed another, websites, email, Matrix, NextCloud, XMPP, IRC, Gopher, Usenet, and a million more are each on their own little webs.
It doesn’t really matter which Lemmy server you pick to join the conversation on Lemmy but your account is only with that server. But because that server is a part of the Lemmy web you can talk to anyone that is also on that web.
That’s the best Eli5 explanation I can give. It’s not particularly accurate because anything, any system, involving more than about 3 people will contain more exceptions than rules. And the fediverse has a lot more than 3 people in it.
My advice for new users on the fediverse is, once you have decided what service (Lemmy, Mastodon, Pixelfed, email, or whatever) either join a server that is most in line with your interests, or look up the largest servers of that service and pick one from the lower end of the top 20.