their business model had any room for 3rd party clients.

Another one: Corporate decisions can change. Bluesky is still dependent on that company and it’s infrastructure. People analyzing its architecture and protocols showed that while some things can be done without BlueSky the company it’s still not feasible or even possible to setup one’s own independent but federating service without using some of BlueSkys infrastructure.
Such dependencies hurt 3rd party clients even before
2/

the takeover of Twitter by Dickhead as certain features were not accessible to them. These dependencies outright killed the 3rd party clients after Dickhead took control and put their business in jeopardy.

So, while I use BlueSky occasionally (read: rarely), I do miss a good client for that social network. That said, I doubt that even with a great client I would make BlueSky my primary home for Social Media.
parker.micro.blog/2025/01/29/w…
3/

To me there are other reasons it seems unlikely I’ll switch from #Mastodon to #BlueSky as my primary social media network. Despite the problems that Mastodon currently has.

On a detail level, there’s the problem with programmatic or algorithmic influence timeline and the easy target it creates for manipulating people.

Then there’s the #dependency company that shares similar roots and vibes with Twitter amid current political turmoil. See also
berthub.eu/articles/posts/comm…
by @bert_hubert
4/5

Communications without Musk and Trump: Cloud Kootwijk - Bert Hubert's writings

In the beautiful Dutch booklet Over en Uit: Driekwart Eeuw Radiocommunicatie 1900 - 1975 (‘Over and out: 75 years of radio communications’), we read: 1916: As a result of British cable censorship, free communication between the Dutch government and t…

^{Bert Hubert's writings}