@jdp23 Are they also using Bluesky's servers for DMs, since those are stored off-protocol?
Or do non-Bluesky AppViews just don't have DMs? (Or whichever part of the stack is responsible for that.)
@jdp23 Looks a bit involved. Interesting read, though, thank you for sharing!
@tom@tomkahe.com @coreysnipes@hachyderm.io @_elena@mastodon.social @stefan@stefanbohacek.online @jaredwhite@indieweb.social
Sorry was a day today.
The web is more tumblr inspired, but the mobile app has a different design and you may enjoy that one instead.
The app is made by a different person with different design ideas!
@jaredwhite Yes, I think that's the big question, whether the larger Atmosphere will survive Bluesky's inevitable enshittification. A year ago, I would've said, probably not.
Today, I don't know. Maybe?
Well there are the people working at Bluesky the company (doesn't seem to be my crowd either) and then there's the development community trying to make the Atmosphere independent from them.
Not super familiar with the second group, other than folks I already know from here, but I do give them some benefit of doubt.
I mean, some of them are doing some interesting stuff, and again, trying to create independence from Bluesky the company. And that's quite commendable.
Yeah, I'd prefer to see them put in the effort here, but fediverse development is arguably more challenging, and with a smaller and less diverse userbase, probably less rewarding.
@coreysnipes I do like that there is interest in implementing some of the better ideas here, things like portable identity, or at least better migration.
But we all know here there is just not enough funding for all the work that's needed.
Yes, Bluesky/Atmosphere is heavily subsidized right, but still, there is a ton of momentum and excitement around it.
There are people putting in the effort to make the ecosystem more decentralized, many don't like how much control Bluesky the company has.
And they might just very well succeed.
You can run some of the ATProto infrastructure on a Raspberry Pi as well, with some of the same trade-offs we have here, like not having the full network view.
https://stefanbohacek.online/@stefan/116126040489956521
Not really trying to advocate for the Atmosphere here, mind you, but there is quite a lot of momentum over there.
And there is definitely progress, even if it's slow. A bit like here.
@_elena there's also no need for SSO (Single Sign-On) to mean “single identity” —as long as YOU are the one that controls the sign-on. See e.g. the Nomad protocol:
Should be interesting
@_elena Interesting point!
Personally, PDSes are one thing I really like about the Atmosphere/ATProto. Being able to log into multiple apps without needing to manage multiple accounts is pretty convenient, and enables more developer experimentation.
Here, you either create a new fediverse platform, meaning you need to create a new account, or maybe a Mastodon browser plugin or web app, because not many want to put in the effort to support all the different APIs.
@_elena @jaredwhite To be fair, it is possible to host all of the ATProto infrastructure for much cheaper with the same trade-offs as with a fediverse server, where you get an incomplete view of the network.
@_elena @jaredwhite That is, with one exception.
Apparently the built-in DMs are stored off-protocol on Bluesky's servers. So, yeah.
(But they are apparently working on that.)