GlitchyZorua 
Alright, I need everyones help on this.
Give me reasons why #bluesky is a terrible platform that shouldn't exist.
Admin JerryYesterday, I set up a #Bluesky #PDS (Personal Data Server). The domain is: blue-ocean.social.
If you visit it, you won't see much other than it saying it's a Bluesky PDS. It has no UI.
Before I go on, PLEASE do not respond about why Bluesky is a POS, evil, the best, the worst, better or worse than something else. This is a technical post for people interested in the technical aspects of Bluesky hosting/federation. I, personally, do not use Bluesky. I prefer Mastodon, for my own reasons. Please don't go off-topic.
#Bluesky just released the first piece of its federated infrastructure that uses their #atproto (#ATProtocal) network, which is similar to ActivityPub in what it wants to achieve.
This first independent Bluesky component is meant for people who do not want their data hosted on a corporate-owned server. Unlike Mastodon where data is kept inside a complete social media platform, in Bluesky the data sits in what they call a PDS (Personal Data Server). It does nothing more than serve as a repository of user data and for keeping account information about the person who owns the data on the PDS. It can do nothing more.
You can create a PDS just for yourself, your family, your friends. You can use someone else's PDS if you just prefer to keep your data on a non-commercialized volunteer-run server, exactly as it is done with Mastodon.
This PDS holds everything that the hosted account posts. All the other PDS servers, and Bluesky corporate servers talk to me. I am part of their network. My Bluesky ID is jerry.blue-ocean.social because the ID contains the PDS server name. However, internally, you are also given a DID, a unique identifier that stays with you, like your cell phone number, and shared across all the servers.
If you move your data to a different PDS, you provide the DID, and regardless of your new handle, the system knows you as the same person you were before.
While my account (identity) and my data are solely managed on my new PDS, I still need to use a separate Bluesky app to log in because this is just a data server, a repository similar to GitHub, where my data gets checked in and where my identity is stored.
I used https://bsky.app to log in with my username (jerry.blue-ocean.social) and password but could have used any Bluesky app to log in.
Setting up the PDS was quick and easy. I have it hosted at Digital Ocean on a 2GB/2CPU 60GB droplet for $18/month. Memory use is at 35% and CPU is typically at .3%.
The instructions to set one up are at https://github.com/bluesky-social/pds?tab=readme-ov-file#faq.
The installation script installs Docker containers. It set up everything quickly. For now, you have to join the admin DISCORD server and give them the domain name for them to enable on the network. In the future, this won't be necessary. They just want to be in touch with early adopting Admins.
The only thing they left out of both the documentation and the set-up script is how to set up the SMTP server. This is important. The PDS is the only server that communicates with users whose identity it's responsible for, so the server needs to be able to send emails. For example, when you confirm your email address in the app, it is the PDS that sends the confirmation number.
Bluesky promises that it fixes some Mastodon issues, like moving to another instance without losing your data should your PDS go down, or the admin kicks you off, but to me, it promises a lot more than it really delivers for this.
Here is an extraordinary blog post about Bluesky that includes how they implement this promise, along with trade-offs about using Bluesky vs. Mastodon: https://lrhodes.net/social/bluesky-portability (@lrhodes)
This PDS release is the first beta, and it comes with restrictions. No PDS can have more than 10 accounts, for now, and is limited to 1,500 events/hour, and 10,000 events/day.
I have 9 more accounts available on the PDS. If anyone wants to use Bluesky without having your data hosted on the corporate PDS, and you plan to actually try using and playing with Bluesky, I'm happy to give you an invitation code. In theory, in the future, you can migrate to any other PDS if you like. So this can be your temporary, or forever home.
Remember, this is beta, and so no guarantee that something bad won't happen, and then you'll lose your data. They make this clear that this is beta software and that people can lose their accounts.
I would like to eventually be able to store data in an S3 bucket and move the database to another server, especially when the 10 account limit lifts. There will be downtime at times while I struggle to upgrade the server and maintain it. Something else to know if you want an account on this PDS.
Admin functions are currently limited to updating to a new version, creating and deleting accounts, password resets, generating invite codes, and a couple of other things. All functions are managed through CLI (command line interface).
If you know of anyone worth following on Bluesky, do tell.
Kyle ReddochLooks like BlueSky is getting into paid services starting with custom domains for users to use with their profile and the AT protocol.
