Angry, disappointed users react to Bluesky's upcoming blue check mark verification system
Angry, disappointed users react to Bluesky's upcoming blue check mark verification system
Bluesky, the decentralized social network, is working on a new verification system, and users are not happy.
You're viewing a single thread.
Bluesky, the decentralized social network [...]
Were only one instance exist or did I miss something?
I think their initial selling point was that Eventually©®™ Bluesky would federate with the rest of the Fediverse.
Is anybody really surprised that a social media corporation didn't make it their utmost priority to allow their userbase to connect out of their proprietary platform?
They never said they'd do so natively with other protocols - but they support Bridgy, so you already can do that.
You can easily host your own instance with a simple docker stack.
I dont know of any public instances except the main but I also havent searched.
you can host your own PDS, but everyone is still using the same appview
As I understand it, the protocol has the ability to decentralize built in. But the technical requirements are prohibitively high to the point only large businesses or corps could afford to do it. I also believe (someone correct me) the company hasn’t switched on the functionality yet.
Maybe you remember PDS federation not being open for a while, but it's open now.
Running a public appview can be very expensive, but they're working on making it cheaper to run one with a limited scope.
The biggest thing is that you need to be manually authorized by them for federation. They will only ever federate with servers that arent serious enough competition to lead to democratization of the overall network.
No, PDS federation is fully open now.
They're also actively supporting development of 3rd party appviews and relays.
my mom has always told me that I had the potential to work at NASA. but the requirements are prohibitively high
I believe in you!
all you need is a work ethic and a time machine
Last heard (a few months ago) the cost is in storage. The protocol isn’t too complicated now, but it generates a shit ton of data, and IIRC you need a minimum of 3 copies.
Storage is cheap whwn it comes to webhosting and 3 replicas is honestly not much when it comes to enterprise standards. I think cloud storage providers like backblaze keep something like 9 copies of data across different mediums
Nope, it's 100% centralized.
It's 100% centralized, but with the ability to be decentralized. Sorta like Threads before they started federating
Sure, but until it actually gets used significantly in that way, we might as well just say it's centralized.
The "ability" to decentralize has costs that scale quadratically. So in every practical sense, it cannot be decentralized. At best it could have a few servers that participate.
No, it doesn't scale "quadratically". That's what going viral on Mastodon does to a small instance, not on bluesky. Pretty much everything scales linearly. The difference is certain components handle a larger fraction of the work (appview and relay).
Both a bluesky appview and a Mastodon instance scales by the size of the userbase which it interacts with. Mastodon likes to imagine that the userbase will always be consistent, but it isn't. Anything viewed by a large part of the whole Mastodon network forces the host to serve the entirety of the network and all its interactions. So does a bluesky appview, in just the same way, but they acknowledge this upfront.
Meanwhile, you CAN host a bluesky PDS account host and have your traffic scale only by the rate of your users' activity + number of relays you push these updates to. Going viral doesn't kill your bandwidth.
This is a little bit more black and white compared with the other responses. 🙈