Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

LinkLonk supports comment notifications for any item that you have subscribed to. You get notified through browser notifications and email. And you can mute/follow individual branches of the comment tree. Details: https://linklonk.com/item/396040801387544576

There is definitely more to improve, but I'd like to see more use of the comments section first to know what needs to be improved next.

As for ActivityPub, I just saw https://go-fed.org/ on HN and it looks like a good fit to add ActivityPub support to LinkLonk (since it is written in Go). There are multiple ways to do it, so let me know how you would like to see it working. Do you want to follow posts of Mastodon users on LinkLonk (similar to how it shows you RSS content)? Do you want Mastodon users to be able to follow your channels on LinkLonk (e.g. @s3000@linklonk.com)?



>LinkLonk supports comment notifications ... can mute/follow individual branches

Great!

>how you would like to see it working

That's a difficult question. My primary focus is on the availability of discussions. Nevertheless, integrating LinkLonk in both directions with Mastodon should help with growth. There doesn't seem to be an algorithmic timeline, which LinkLonk could provide. Establishing LinkLonk as an integrated RSS Reader and ActivityPub Client could attract a bigger user base that makes calculating suggestions easier.

What ActivityPub can bring to new social networks like LinkLonk is the ability to share the comment section with various other providers. E.g. RSS readers or annotating browser plugins can pool their comments in one place to have an active discussion even if each tool has a small user number.

However, pooling discussions is generally avoided:

1. When there is a dupe on HN, the discussion in the old submission is not continued.

2. There exist various aggregators like lobste.rs, reddit.com/programming or tildes.net, that almost discuss the same articles as HN, but they are different communities.

3. Twitter and Mastodon could pool the replies to posts of the same url, but they don't.

The trivial approach for LinkLonk would be an integration with lemmy.ml and all Mastodon posts that discuss the same URL. That way, most posts would come with a discussion and LinkLonk instantly had a vibrant community.

With the pool-avoiding behavior in mind, some adjustments could be needed but I haven't figured out what that could be.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: