

Yes, you can host your own PDS server, that is known and stated.
The entire design of a lemmy instance is meant to be more ‘self contained’, as I already mentioned. This is what enables the federation network to organize in a ‘many to many’ connection style, as opposed to a ‘many to one’.
A lemmy instance roughly has many/most of the capabilities of a PDS, Relay, and AppView… all rolled into one.
This is a fundamental difference of a ‘true’ federation model… all the members of the federation are capable of operating independently.
If you are in a federation of unequals, with built in dependencies… your ‘federation’ is much more like a king with vassal states, not a voluntary association.
Yes, migration of a user account from one instance to another would be complicated… but … so would migrating a user from one PDS to another.
I don’t even know how you could fully ‘migrate away from BlueSky servers’… when BlueSky run the only Relays.
Also, many (most?) actual client apps for viewing lemmy, posting on it, etc… they pretty much hold a lot of your particular user customizations, at least as it comes to visual theming, independently, locally, not even related to the actual user account on an instance you are using.
They also support easy switching between different lemmy user/instance accounts…
…
Also also, as far as I am aware… if you have an account on a lemmy instance, you can delete your account and this will wipe out all of that account’s posts and comments across the whole fediverse, aside from modlogs and internet archive web snapshotting type stuff.
I … think you can also export your own data as well?
Not 100% sure on these last two parts, maybe an instance admin or powermod could chime in… but I think this is correct?
… Yeah, as 73ms already pointed out… that first link is just someone setting up an AppView.
To truly run an independent BlueSky system… you would have to run your own PDS, your own Relay, and your own AppView.
Your second link does actually have code and a rough setup guide to running your own Relay, so I will give you thanks and credit for showing that at least it is possible to theoretically do this…
But you say ‘several people run their own Relays’ and then do not evidence that.
The Relay config here is just… how to host your own Relay that would act as a member of BlueSky’s Relay network.
Basically, that is just how to transfer some of BlueSky’s server hosting costs … to yourself.
If you set up a totally independent Relay… could it even interface with BlueSky’s Relays?
As far as I can tell: No.
It would be totally independent… a parellel network, not a federated one that interfaces with the rest of BlueSky, and is thus not actually able to ‘federate’.
What… you would have to do… is set up your own Relay, connect it to basically all the other preexisting PDSs you want to include, then also run your own PDS, then also run your own AppView, and connect it to your own Relay… or just trust someother person running their own AppView, or just trust the official ones.
(But… I think that to connect your own Relay to preexisting PDSs… that would require those PDSs to… disconnect from the mainline BlueSky Relay system… because they can only point to one Relay system at a time… so that’s kind of a problem.)
That would be the only way to make your own … sort of branch of the BlueSky system, that at least in theory might be resistant to centralized censorship from BlueSky.
And again… I am not aware of anyone who has yet done this, or if it would even work at a technical level.
When dealing with software and tech companies, a good rule of thumb is that a planned or possible feature… doesn’t actually exist untill its been provably demonstrated to exist and work.