Thread of 7 posts2 min read
Why Frontpage doesn't show Bluesky comments
When we were first building Frontpage we went back on forth on whether to include Bluesky comments. One possible vibe for Frontpage was a collation of all discussion around a specific link. It still is tbf, and maybe some day we figure it out but it turns out to be a really hard UX problem
Bluesky post· 17.12.2025, 08:12As soon as you show threads from more than one source you run into a bunch of challenges and questions Firstly, should a user on Frontpage be able to interact with these comment threads from external apps?
If you answer yes then it leads to questions around user intent. How do you make it clear to the user that they are participating not just on Frontpage, but also on this external app. That app could have different vibes but also technical stuff like comment length has to be considered
It also presents a problem of permissions; Frontpage would need permission to create Bluesky records. This would need to be carefully designed (maybe as an additional consent flow) and explained to the user, it could weird some people out
Another technique could be to present these threads as read only, with the Frontpage comments as the only place where you can participate in the discussion. This is quite the design challenge because it fuses two different intents: participation and discovery.
I think to sum up - a lot of this problem space collapses and becomes easy if you just use a single source for comments, like Bluesky. In the end, apps want the ability to create their own conventions, community, vibes, memes etc.
Adopting multiple sources dilutes this ability and could force the discussions into some lowest common denominator territory, or just enhance Bluesky's centralisation powers