Can also piggyback off / strangler fig existing website structure. Ex. bookmarks to titles on goodreads.
Add in a similarity graph (people also bookmarked x), and a democratic way to merge bookmarks that point to the same object.
And if you want to get really nutso, add a resource management system where ppl pay for attention - mint bookmarks as NFTs, commenting has a cost, invest in a bookmark to boost global visibility and get a % of commenting cost
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
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
How did your project turn out?
