https://futureofcoding.org/ logo
Join Slack
Powered by
This post exemplifies why I am quite excited by at...
# linking-together
t
This post exemplifies why I am quite excited by atmosphere, in multiple ways. https://bsky.app/profile/sebastian.eurosky.social/post/3mljcco2i3s7v Cloud data sharing across apps, and the author has their social data hosted on European servers.
šŸ° 2
Oh interesting the link unfurling doesn't work, did the author consciously do that or is that the European PDS?!
šŸ‘€ 1
k
All that is very promising indeed. But I wonder which percentage of ATProto-based apps is fully independent of BlueSky. So far, everything I have tried asks me for BlueSky authentication.
t
Early days but Sifa is a euro linked-in like https://sifa.id/compare/linkedin on atmosphere and eurosky interop
šŸ‘€ 2
šŸ‘ 1
OK I fixed the auth on Lopecode. No BlueSky permissions! Can only write to com.lopecode.bundle (I will need to expand that later, I wonder if I can do 
com.lopecode.*
)
ā¤ļø 2
wildcards kinda work but not the oauth popup so maybe later
d
ATProto has a lot of exciting demos being built on it, the PDS/Pod is an excellent idea but I'm still fuzzy on how it'll play out when it gets adversarial. I.e. ut hasn't been tested yet.
k
My view of the atmosphere as an interested outsider is that there is a good set of core values around data ownership, but they remain abstract beliefs that are recited, but not turned into working code. Actual code development seems more motivated by the values of the "traditional" tech community: we the experts build tools for the less sophisticated masses. Example: What would it take for me to really own the data in my PDS? Today's reality for most people is that they choose between two or three PDS operators. They know they can somehow move between them, but figuring out how to do it is hard. Data ownership would also require that users can make personal backups, and restore them with a different PDS operator if necessary. I have tried to find a tutorial for that, but failed so far. This isn't an issue with @Tom Larkworthyā€™s Lopecode, because I can keep HTML copies of the notebook. But I don't see myself as really owning my BlueSky posts and Semble cards. If EuroSky closes down tomorrow, I will lose all of them.
šŸ’­ 1
d
Fair criticism @Konrad Hinsen though I reckon the solution here is simple. For example, I have a small TODO for thise extensible personal database app I'm making to write a plugin that backups PDSes periodically. In sure someone will end up providing such a simple service at some point.
That being said, this is adjacent to the issue of an app deciding to store critical bits of data in its proprietary databases that it controls. There was a post related to this shared recently at https://www.orionreed.com/posts/app-file-topology/
šŸ‘ 1
Especially with VC funded apps in play (and a lot of competitors I bet), this is just begging to happen. Any app that makes money is incentivized to do so.
I'm personally hoping this problem would lead ATproto to be the cradle of an alternative standard to VCs for computing infra organizations but we shall see.
k
In a VC-funded world, we are likely to see backup-as-a-service, but not personal data ownership. Of course, backup-as-a-service is preferable to the current situation as long as the backup service is independent of the PDS hosting service AND this independence is transparent to users and guaranteed to persist. Which, unfortunately, is unlikely in a VC-funded world.
Open in Slack
PreviousNext
Powered by