The Bookmarking Data Model Is Wrong for Highlighting
lgug2z.com
lgug2z.com
I find the HN discussion often adds a lot that will be relevant. For example, in `~/wiki/machine-learning.md` the section on specific LLM models is a nested bulleted list, with the top level the names of specific models (sometimes as links to their canonical landing package, and the bullets under each are usually very relevant HN post links, and links to official other pages for that model.
I only polish it when I really have to: the priority is to capture the info, because 15 seconds now might save me days or an entire endeavor later. But spending more time than that can discourage capturing info, or later make me resistant to doing a quick split of pages or sections that really should happen immediately (because I don't want to spoil the polish that I spent time on).
In Markdown, my current HN post links look like:
[HN, The Bookmarking Data Model Is Wrong for Highlighting (lgug2z.com),
2023-05-16](https://news.ycombinator.com/item?id=35964335)
(My Emacs mode hides the URL part, and makes it look like an underlined blue hyperlink, with the remaining markup characters de-emphasized.)It's a variation on the familiar citation format, which I also use:
[Jane Doe, "Some Article Title", *Some Journal*,
2023-05-16](https://journal.example/12345)
In the rare case I want to quote an entire HN comment in my wiki (e.g.,, some super-useful insider scoop that might disappear), I'll just click to its page, select it and copy&paste the test with `>` characters, and then turn the header line into a Markdown link to the comment page URL.Someday, I'll make a browser plugin for the copy&paste parts, while still keeping it very simple.
The distinguishing feature of highlights is that they are anchored to a specific passage in a (hyper)text, which you want the bookmarking tool to make visibly distinct, searchable, and so on. Ideally you want this feature to work seamlessly across paginated texts as well as on PDFs.
Comments are an entirely different animal, and the way they do (or don't) interact with highlights will depend on how people use the site socially, which is not really within the control of the site author.
Binning bookmarks, highlights, and comments together as "content" is like calling wedding cake, bobcats and lighter fluid different kinds of "matter"; it's reductive to the point of uselessness.
> This discussion conflates comments with highlights, which are two different animals altogether.
And this
> The distinguishing feature of highlights is that they are anchored to a specific passage in a (hyper)text
And this
> Comments are an entirely different animal
And this
> Binning bookmarks, highlights, and comments together as "content" is like calling wedding cake, bobcats and lighter fluid different kinds of "matter"; it's reductive to the point of uselessness.
I find this part important but misleading. The URL is a fine way to identify the article, but it's important to separately identify and link to the multiple discussions that can be had about any given article. For example, an article URL doesn't unambiguously identify a HN discussion as the same URL is submitted and discussed multiple times.
Rather, this may be the gist of OP: Because we post URLs without top-level commentary here, the HN discussion (and HN URL) isn't a single, meaningful conversation either. Only when we get to each top-level comment (identified by the comment URL), we have conversations that it may make sense to highlight.
People share collections of notes / highlights / bookmarks with their team. Public collections live here: https://histre.com/public/collections/ but you're right that highlights of one user are hardly useful for another random user. It is extremely helpful for the team that's working on the same project though.