![](https://media.kbin.earth/60/e8/60e840340623364592a12619a592e2524aefbca1cba9498a6e7df82e68c379d1.jpg)
![](https://lemmy.world/pictrs/image/eb9cfeb5-4eb5-4b1b-a75c-8d9e04c3f856.png)
I think in some ways Mastodon is better suited - if you use the list feature actively there, it gets quite powerful. And personally I quite like the way content gets community curated on Mastodon once you follow enough people.
I love Mbin, but scratches a very different itch. :)
If I understand correctly, there’s a central pump running behind the scenes in any AT implementation. You feed content into the central hub, and it pumps it out to everyone connected to it. Bluesky itself provides the one major pump that feeds its network right now.
So in that sense, Bluesky is a centralised network with decentralized users.
Frontpage is building a different pump, spreading different kind of content to a different type of platform. So there’s no obvious connection between the Bluesky pump and the Frontpage pump - that’s why they’re talking about bridging in the post.
It almost seems a bit silly - in order for two AT hubs to talk, you need to build a bridge for them. At that point, you could might as well have built an AP protocol and made it work with Bridgy.fed.
Furthermore, all “instances” running Frontpage would process data through the same central hub. If that goes down or they run out of funding, it’s all over.
I’m applauding the Frontpage crowd for trying something new. But I’m not entirely convinced I see the benefit compared to what we’re doing over here.