Why just invert, when you can offer multiple view simultaneously ? :
1- We keep the r/whatever (subject matter) stream like view
2- We can always have that enhanced "saved bookmarks" view you talked about. They are not mutually exclusive.
3- To expand on your "reference page" (Wikipedia-like) idea, the bookmarks should be more malleable: We ought to be able to collaborate on reorganizing them under different tag-systems/hierarchies (while they keep their original comments and score)
So it is 3 complementary views: stream view (current Reddit/HN link-posts), personal view (current bookmark managers), and reference view (a more structured “awesome lists”)
Most sites do have at least two (mostly 1+2), but one at least is always rudimentary (like the HN favourites). I myself tried to combine 2+3 (for a private team) using the coda raindrop pack https://coda.io/packs/raindrop-io-11475
Yeah, good points. #3, "tag cloud" idea is great, and lends itself to view by tag.
I'm coming at it from the direction, where I see the primary action as "collecting" / "cultivating". Ex.
1. See an article you like
2. add it to bookmarks/instantiate the global bookmark
3. curate it a bit - add an archive link, some tags, link to related article
and then the reward is
4. get notified when someone else bookmarks it + comments, a week or a month later
so the inversion is - on HN/reddit, something gets posted once and there's a big discussion and it disappears. this is the opposite where the page grows over time
Yesterday, a Show HN [1] was an RSS reader that displays related HN/Redddit comments. I can imagine bookmark managers alerting you in a similar fashion. It will not be as integrated as you specified (single thread by link...), but the scale will be much bigger : Theoretically you can link it (crawl/api) to any site, then you get a dashboard+notification on your existing bookmarks for new
- discussion threads (HN/Reddit...)
- annotations/notes (Hypothesis.is...)
- reviews (alternativeto.net...)
My coda/raindrop "project" is just a "doc template" we use sometimes to organize bookmarks in a small team. It is not supposed to scale beyond that. Many Coda features [2] come handy.
The closest thing I've seen is https://ampie.app/, which goes in a similar direction. I bounced off of it (too cluttered, privacy concerns w browser extensions), but it has a lot of the pieces there.
1- We keep the r/whatever (subject matter) stream like view
2- We can always have that enhanced "saved bookmarks" view you talked about. They are not mutually exclusive.
3- To expand on your "reference page" (Wikipedia-like) idea, the bookmarks should be more malleable: We ought to be able to collaborate on reorganizing them under different tag-systems/hierarchies (while they keep their original comments and score)
So it is 3 complementary views: stream view (current Reddit/HN link-posts), personal view (current bookmark managers), and reference view (a more structured “awesome lists”)
Most sites do have at least two (mostly 1+2), but one at least is always rudimentary (like the HN favourites). I myself tried to combine 2+3 (for a private team) using the coda raindrop pack https://coda.io/packs/raindrop-io-11475