In the article, they outline how Blue sky is resistant to that path through the PBLLC structure and ability to move your account when you don’t like the web site.
Time will tell if this model works in practice but it could be interesting as an alternative to Twitter without the usability issues normally associated with federation.
I won’t knock BlueSky for trying. I think it will go well to replace Twitter, and run strong for some years. I’m still a bit on the skeptical side, especially until we see the ActivityTracker protocol on a non-BlueSky server in action, that BlueSky won’t be bought out and puppeted by some wealthy group.
That is also part of people’s worry if one instance gets way too big on Lemmy, Mastodon etc. There is potential to change their federation scheme, closing themselves off from outside servers through unique features made incompatible to federate, eventually returning to a centralized model of its own.
If the API standard is dictated by a for profit, there’s always the chance that at some point it’ll incorporate unfavourable features or impose limitations. To me Chrome/Chromium comes to mind, or even ‘embrace, extend, extinguish’. I’m not familiar with pbllc though, it might be different, but I’m sceptical all the same.
In the article, they outline how Blue sky is resistant to that path through the PBLLC structure and ability to move your account when you don’t like the web site.
Time will tell if this model works in practice but it could be interesting as an alternative to Twitter without the usability issues normally associated with federation.
I won’t knock BlueSky for trying. I think it will go well to replace Twitter, and run strong for some years. I’m still a bit on the skeptical side, especially until we see the ActivityTracker protocol on a non-BlueSky server in action, that BlueSky won’t be bought out and puppeted by some wealthy group.
I can see a potential path for it’s downfall.
That is also part of people’s worry if one instance gets way too big on Lemmy, Mastodon etc. There is potential to change their federation scheme, closing themselves off from outside servers through unique features made incompatible to federate, eventually returning to a centralized model of its own.
If the API standard is dictated by a for profit, there’s always the chance that at some point it’ll incorporate unfavourable features or impose limitations. To me Chrome/Chromium comes to mind, or even ‘embrace, extend, extinguish’. I’m not familiar with pbllc though, it might be different, but I’m sceptical all the same.