The value is in the granular way that you can connect communities. You’re totally right that there are a lot of cases where there are good reasons not to connect communities. That goes across instance borders (like you said, Beehaw and Hexbear would preferably not connect communities), but even for instances that are similar, not all communities need to be connected. In the current example of the Social Hub forum and the NodeBB development forum, only 2 communities (categories) are connected, and the rest is not.
Oh thats an interesting question! I’m assuming you are talking about the UX/UI of instance selection?
And thats not something I have written about (neither does another article pop into my mind either sadly), but interesting idea for an article for sure to write about
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:
yeah its great to have more managed hosting options. The UX is also really well done, which is great and something I dont see to often in these places. Need to get some time next few days to start up a new lemmy project with this
ha yeah I remember that, that was fun.
To riff on this a little bit further: its also visible in how little attention in the gazillion conversations about Threads is paid to the fact that the entirety of the EU cannot even access it yet due to the new DMA and DSA.
Or one of the articles I wrote that got relatively low traction, that was specificially about how all of the Nordic countries got an official recommendation to use ActivityPub for their governmental communications. I dont mind that some articles get less traction than others, but it does stand out when you consider how impactful such things are for the long term structure of the fediverse. Lots of EU governments are now talking about needing sovereign public digital spaces, and are actively looking how ActivityPub can help with that. And that matters way more than whatever Elons latest shenanigans are.
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/