Erlend Sogge Heggen @erlend.sh · Dec 17 Still feels like a critically missed opportunity for @leaflet.pub to not interop with Bluesky for comments. For someone who discovered this article via leaflet itself or any medium other than *sky, there’s absolutely no sign of the generative discussion that ensued on-feed, nor its likes/shares. 🧵
62 likes 10 replies
Replies
as with @stream.place use cases, i can't help but feel that the right answer is: either. allow users to do either. allow their comments to be regular posts, or let them be leaflet/stream.place comments.
the way I intend to do this with weaver is to allow people to add an embed for [platform of choice] comments, with the initial option being a linked bluesky post. and similarly to then track likes on that as if they're likes on the actual piece (both mine and bsky lexicons valid).
I’ve been banging on a similar drum ever since the first day I found out about Leaflet. Comments on the web have been broken for such a long time. Bluesky and the AT protocol offer a way forward for “engagement consolidation” (and icky term for simply “having your conversation in the same place”).
Yeah agreed @leaflet.pub
Thanks Erlend, appreciate this! I don't think it's a binary & we can def improve while keeping distinct @leaflet.pub comments We actually have a way to view associated Bluesky posts (both the one linked on publish & others that link to the Leaflet). But a bit hidden & doesn't show full discussion.
i dont think everything should depend on bsky but it could be nice for those comments to also be shown (ideally with some api on the leaflet side so i can use that, heh)
main reason I didn't use leaflet yet. I'm not popular, so splitting all the engagement just makes it worse lol
I don't know, I'm kind of with leaflet on this. Why should leaflet have to cave and just do whatever Bluesky is doing? Is the bsky AppView adding leaflet post previews? Are they incorporating other lexicons? Really feels like a double standard that we need to stop enabling.
Another strong case for more direct interop:
I don’t want the custom comments; I wanna consolidate engagement. That means defaulting to bsky for comments. That could work by simply auto-connecting my leaflet article with the first bsky post by the same account containing that link. That’s the canonical comments thread. Also canon for likes.