Heya! Good answers earlier by you!
Yeah I think I’ll have to get into that, but I’m starting to run into the limit of not being a programmer myself, and information is pretty scarce on ATproto. The article differs from their own federation architecture description from earlier in the year, simply because its outdated and noone has formally written down the new info, so that was a bit of a struggle haha https://blueskyweb.xyz/blog/5-5-2023-federation-architecture
At any rate, the PDS’s are amenable for sure. Robin Berjon is the furthest along with thinking here, with his AP over AT piece: https://berjon.com/ap-at/ Responses I’ve seen havent suggested its technically impossible, but probably difficult for reasons that I tuned out of reading because I didnt understand :D
Beyond that, people keep talking about the lexicon and how that at is core is also versatile; similar to how fedi has Mastodon’s type=Note that everyone uses, even though you can create any ‘type’ you want. I’m pretty sure that nobody has done that yet tho.
I actually set out to answer this question in a blog post, but it turns out that the answer is quite complicated, so I have to write an entire series about it. First part I published this week, which explains all the different components that make up the Bluesky network:
https://fediversereport.com/how-bluesky-works-the-network-components/
I don’t think that they’ll run into the exact same problems that AP-fedi has, as the design decisions are often made specifically to avoid some of these. However, their design decisions create new sets of problems for the network, which I’ll get into later
Strongly agreed.
Some other loose thoughts related to this:
Thank you for sharing the article! Please note that this is last’s weeks episode, the newest episode went out yesterday: https://fediversereport.com/last-week-in-fediverse-ep-70/