![](https://lemmy.ml/pictrs/image/apcQ8xodn6.png)
![](https://lemmy.ml/pictrs/image/gWmVEUZ94Z.png)
For the love of god, listen to some Citations Needed and stop self-congratilating your media literacy because some fucking dork with a website tells you the New York Times and Washington Post aren’t biased.
Hexbear enjoyer, absentee mastodon landlord, jack of all trades
Talk to me about astronomy, photography, electronics, ham radio, programming, the means of production, and how we might expropriate them.
He/Him
For the love of god, listen to some Citations Needed and stop self-congratilating your media literacy because some fucking dork with a website tells you the New York Times and Washington Post aren’t biased.
The politics of folks like RMS (personal issues aside) were far above average, but the Free Software Movement was very steeped in liberalism from its onset, and that explains many of of its present shortcomings. Its biggest failing was to believe that Free Software would ultimately win on its merits. In the early days this was understandable, when free software was often playing catch-up to replicate the functionality of established commercial offerings. When the GNU project was just a C compiler you could install on proprietary UNIX systems to dick around with.
Today though, Free Software is more often than not superior to commercially available offerings, with the exception of some niche industrial segments. But still, Free Software adoption by end users remains incredibly marginal. No matter how many merits Free Software stacks in its favor, the “Year of Linux on the Desktop” never comes. We are still drowning in proprietary iOS and Android phones. The overwhelming majority of PCs still ship with Windows. All of it deliberately engineered to become E-waste in a couple of years.
Folks, this won’t change unless we take over the factories where these PCs and phones are manufactured.
This is not true. ActivityPub (the protocol Lemmy instances use to speak with one-another) does not intend to be a redundant, distributed datastore. There are a few reasons for this. One is practical. It needs to be affordable to start a new instance. If the requirements for starting a new instance entail mirroring significant parts of the fediverse (a network of over 2 million users and 22,000 instances) it would be impossible for anybody to do it unless they were Google/Facebook.
Another has to do with trust. A community has a home. That home is chosen (ideally) because the admins can be trusted. That instance is the universal source of truth for that community. If communities didn’t live on a specific instance, they would be vulnerable to various forms of hijacking. The home instance has the final say on who has permission to comment, and who has permission to perform moderator actions. None of these actions could be trusted if they weren’t cleared by the home instance first. Third party servers perform basic validataion against the currently known ban list / mod list / etc, but this could easily be spoofed by malicious instances.
When an instance goes down, it is kind of similar to a netsplit on IRC. A queue of outgoing messages build up on your instance, which can be seen on your instance. Queues of messages queue up on other instances, which can be seen on other instances, but they won’t be synchronized until the destination instance returns (this depends specifically on which inbox the messages are directed towards - I’m not particularly familliar with the specific implementation in Lemmy).
Finally (though not really), ActivityPub isn’t designed to be a broadcasting protocol. In the case of Lemmy, and other Reddit-like clones, it effectively acts as such, but it is intended only to send messages to the places they belong. If you post a message and the subscribers to that message only exist on 3 servers, that message ONLY gets sent to those three servers, even though there are thousands of servers in the network (at least, this is how it is supposed to work in theory).
I might have some details wrong here. I’m more familiar with how Mastodon works (and how it fails) at this point after troubleshooting various problems on my instance.