Live data from Hacker News

Bookmarks.txt is a concept of keeping URLs in plain text files

github.com

141–150 of 161 posts

Re: Bookmarks.txt is a concept of keeping URLs in plain text files

#144

Earlier quoted context omitted.

I can't stand having more than a dozen or so tabs open, let alone hundreds. And I might not want them to keep state, but I could see how a "snapshot" bookmark could be very handy, so why not have "bookmark tab" automatically save the state? Or heck, let me drag a tab onto my bookmark bar. We already have the technology, but the UI around it has barely evolved in 20 years.

For what it's worth, you can drag a tab onto your bookmark bar, at least in Firefox.

Nifty, hadn't noticed that. I only switched back to Firefox as my daily driver a few months ago after a long time with Chrome, so I'm still finding new things.

Now we just need it to save the page state like it would for an unloaded tab. But I guess the hard parts of that aren't really implemented after all, all kinds of issues though with serializing the page state, making it work with sync across platforms, or just dealing with someone trying to open the same state multiple times...

Re: Bookmarks.txt is a concept of keeping URLs in plain text files

#145

I do this, albeit, kinda a Start Page. I like it because it is plain-text, and I can access it from any browser (not just the ones I bookmarked with). Mine is online (rendered client-side) so I can access it from anywhere. https://start.oinam.com Just in case, anyone wants to look the source is at https://github.com/oinam/start

I just track my bookmark as Awesome https://wener.me/notes/tags/awesome

The source is at https://github.com/wenerme/wener

I found it's very useful, especially the license and basic tech stack & description. One day I will grab the meta and display along with the link.

Re: Bookmarks.txt is a concept of keeping URLs in plain text files

#146
post #15
post #8

Mozilla-based browsers used to (before Firefox 3, I believe) store bookmarks as HTML (bookmarks.html) instead of using an SQLite database. It still uses a single HTML file when exporting or importing bookmarks.

I was wondering if someone else would remember this.

I also remember that the first web based forums used a Perl script that actually created new HTML files on the web server when someone posted a new topic, and modified the existing one when someone posted a reply.

A bit similar to static web site generators today, only with endless security vulnerabilities.

Re: Bookmarks.txt is a concept of keeping URLs in plain text files

#147
post #15

Earlier quoted context omitted.

I was wondering if someone else would remember this.

I also remember that the first web based forums used a Perl script that actually created new HTML files on the web server when someone posted a new topic, and modified the existing one when someone posted a reply. A bit similar to static web site generators today, only with endless security vulnerabilities.

You might be referring to the venerable wwwboard from Matt's Script Archive, which amazingly still exists: https://www.scriptarchive.com/wwwboard.html

Re: Bookmarks.txt is a concept of keeping URLs in plain text files

#148
post #147

Earlier quoted context omitted.

I also remember that the first web based forums used a Perl script that actually created new HTML files on the web server when someone posted a new topic, and modified the existing one when someone posted a reply. A bit similar to static web site generators today, only with endless security vulnerabilities.

You might be referring to the venerable wwwboard from Matt's Script Archive, which amazingly still exists: https://www.scriptarchive.com/wwwboard.html

It's been almost 30 years, so my memory is hazy, but that really looks like it.

It still exists but last updated in 2000. It might be fun to make a Docker container with the right dependencies (if that's still possible) to run it.

Re: Bookmarks.txt is a concept of keeping URLs in plain text files

#149

(Probably skip if you don't want to read a ~rant..) Questions: - New "format"? It is a CSV with spaces as separators and no header? Why? - Global file located in the home directory? Why would you want another file to pollute the $HOME? Why not just $BOOKMARKS_FILE or something? - Local bookmarks file - why don't just reuse README.md? Add 'Resources' section and chuck markdown links in it, parsing that is not (much) h…

The format itself is not as useful as the unix-like shell oneliners one crafts around it. The inflexible simplicity is therefore the point. (and also it's easy to modify manually)

Re: Bookmarks.txt is a concept of keeping URLs in plain text files

#150
post #102

Earlier quoted context omitted.

> The thing is - I just saved bookmarks, I never really utilised them ever, to find something, to go back to. You're not describing a bookmarks issue. You're describing a personal organization issue, which is reflected on how you manage bookmarks. You're voicing the exact same sort of complains often directed at todo lists. In fact, from your description you're implicitly treating bookmarks as ad-hoc Todo lists, and…

Because it represents wasted time and cognitive load. It's a vestigial habit from an era when search was bad. Between (AI) search and browser history, I don't see much need for bookmarks.

> Because it represents wasted time and cognitive load.

No, not really. Either you use them because they are presented to you, or you don't and you are oblivious to their existence. There is zero cognitive load.

> It's a vestigial habit from an era when search was bad.

Nonsense. It's absurd to even suggest that it's reasonable to use a search engine to be able to open sites that matter to you personally.

Post reply on HN