It's not, but they're cowards
Natanael
joined 8 months ago
The Green Hornet too. Using speculations from a journalist to make plans.
It wasn't for the victims, it was for the perpetrators. Their soldiers would take too much emotional damage from mass scale murder and break down, so they created new ways to mass murder without putting them face to face
Those grow in gas chambers
Fediverse servers can quickly get more expensive if you have a few thousand users, or even a few dozen but somebody has a post go viral. That's because every retrieval of a post always goes to the original user's server, every like does too, etc, and this generates a flood of events which quickly gets expensive to process.
Just ask the maintainers of the botsin.space Mastodon server who couldn't afford to keep it running, and now put the server in archival mode and not allowing new posts.
A PDS only publishes static data and don't have to process incoming events, making it very easy to run one behind a caching server very cheaply.
There is another problem: these other relays are all copies of the Bluesky relay, where the official app publishes the messages of its users, so they are not independent from each other; if I publish my posts on a relay other than Bluesky's I will not be able to communicate with them.
Not entirely correct.
Every individual users' account host (PDS) publishes directly locally, the relay then collects published posts from known PDS servers (including both bluesky's own and others' self hosted servers) and display everything. A PDS server can sync to multiple relays. Relays can even sync to each other, which is practical because PDS servers publish through content addressing for posts in user repositories so it's easy to verify completeness.
So sure if somebody uses an app connected to a filtering / partial / out of sync relay they might not see everything. This is not an architectural limit in the protocol, however.
A split would create North Korea 2.0
The appview needs to index the relay contents to build a view of the whole network, the relay is just a type of CDN, and is NOT that expensive. There are multiple individuals maintaining full copies right now, while the network is at double digit millions of users. The relay is by far less expensive.
You're looking at poorly matched cloud options in that article. The individuals doing it does it easily on a NAS and equivalent. The cost from running public relays will come from traffic, not storage
It's the appview that needs to be made lighter, and that work is progressing. Like building variants you can self host which are selective and only care about content from your network (and only fetching other content as needed)
There's work ongoing right now in making it easier to run a small appview, and the relay is cheaper to run than the appview and very manageable by even small companies
The military does tons of stuff over public networks, the key is using vetted hardware and their own VPN and communication tools which allows complete control over recipients.
No random unaudited consumer devices which might have various exploits known to outsiders, which might fall into the hands of spies, and which DEFINITELY does not have any active security monitoring.
Wrong hardware!
The encryption still works roughly the same, the difference is mostly visible metadata.
Multiple bundles of encrypted message + decryption key & recipient tag for 1 person, or one bundle of the encrypted message and then keys for multiple people & recipients which the server can separate out when relaying the message
(message keys are encrypted to each recipient's keypair*)
*simplified because I can't be bothered to explain how deniability is implemented. Just look up the Signal protocol's ratchet
Appealing bans by suing them over first amendment right to petition (yes it covers more than freedom of speech)