Who owns Bluesky?
Uncategorized
25
Posts
10
Posters
0
Views
-
@mousey Yes, it's very likely that I'll use Bluesky to access the ATproto network, which is the most likely option nowadays. When I create my own app, lexicon, PDS, AppView, etc., the data doesn't necessarily go through Bluesky. It can, as it's open data, but it doesn't have to. If users and app creators get the impression that Bluesky is somehow exploiting their interactions, it's not so difficult to bypass Bluesky and even fork the protocol. Am I right?
@rzelnik Pretty sure that's incorrect. Pretty sure ATProto is specifically designed so that all data flows back to bluesky centrally, before being distributed to the rest of the network.
What you're describing is ActivityPub, which has no concept of "phone home" to a central authority or repository.
-
Who owns Bluesky?
The curious mystery of the Bluesky Series B funding round.
Did it happen?
If you look at pitchbook (https://pitchbook.com/profiles/company/484831-81) it seems Bluesky closed a whopping $97 million funding round resulting in a $700M valuation in January 2025. VCpedia lists Greylock, alumni ventures and Skyseed as participants (https://vcpedia.com/rounds/5195).
The interesting thing is there are no press releases or other media coverage confirming this financing.
Read on...
1/2
RE: https://mastodon.social/@ikuturso/116085318733368362
@mastodonmigration This might be of interest since you've been asking these questions about Bluesky's ownership. Doesn't reveal any new owners of Bluesky but sheds some more light on one of the major ones we do know of.
-
RE: https://mastodon.social/@ikuturso/116085318733368362
@mastodonmigration This might be of interest since you've been asking these questions about Bluesky's ownership. Doesn't reveal any new owners of Bluesky but sheds some more light on one of the major ones we do know of.
Thanks! Knew about Brock Pierce, but not that he was a member of the Epstein gang.
-
@mousey Yes, it's very likely that I'll use Bluesky to access the ATproto network, which is the most likely option nowadays. When I create my own app, lexicon, PDS, AppView, etc., the data doesn't necessarily go through Bluesky. It can, as it's open data, but it doesn't have to. If users and app creators get the impression that Bluesky is somehow exploiting their interactions, it's not so difficult to bypass Bluesky and even fork the protocol. Am I right?
please consider that an open protocol did not stop Google from taking a lot of power over the web by becoming the place most went to search it. based on AP already existing and bluesky then rolling out their competing protocol AT that makes everybody using their app view provide the best experience, I think this is their strategy. use VC to dominate the space and make everyone think of AT as the open social protocol with them as the best experience. enshittify.
-
@mastodonmigration @blackbird Ethernet and Token Ring are another good comparison.
Feed RSS
Gli ultimi otto messaggi ricevuti dalla Federazione
-
-
@macfranc @astronomia ricordate di acquistare solo costosissime auto elettriche per combattere l'inquinamento.
-
-
@virtuous_sloth @scottjenson actually, it doesn't separate the composition of private mentions from other types of posts. It's an option on the drop down. If you forget to change the option, your PM goes out with the default visibility -- often public!
-
@evan @scottjenson
phanpy does a great job
-
I think some people were using PMs for potentially sensitive info (addresses, Venmo, etc.), and having them slightly more secure puts people at ease.
What about standard public-key stuff, dropping a short public key in a metadata field, keeping the private key on the endpoint or in the client?
-
@scottjenson not at all critical.
Hint: you could re-run this as a poll, for the question.
-
@evan the already improved UX looks good, to me.
When drafting a reply to a public toot, the word 'Public' is prominent (first screenshot).
When drafting a mention, the separation is clear (second shot).
Without being blasé about privacy: if a person accidentally publishes in either of those contexts, it's human error.
