Live data from Hacker News

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

github.com

11–20 of 161 posts

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

#11
Given that the aim is to still visit the URL, this appears to be browser bookmarks with extra steps. I am not seeing an advantage to the external storage mechanism and the overhead it brings.

Browsers have been doing an excellent job of managing bookmarks, you can tag and search for them from the address bar itself which is very convenient.

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

#12

Given that the aim is to still visit the URL, this appears to be browser bookmarks with extra steps. I am not seeing an advantage to the external storage mechanism and the overhead it brings. Browsers have been doing an excellent job of managing bookmarks, you can tag and search for them from the address bar itself which is very convenient.

Well, actually I could see a use for this in specific context and use cases, for instance if you happen to have different dev environments you're able to just move from machine to machine while keeping all the bookmarks in the repository.

If you organise them you can even reference them from the codebase, or the documentation to avoid clutter. The format is simple and dumb enough so that a simple bookmark.txt can be converted into a dictionary, array that can be used in the program if some URLs are supposed to be used there.

It's not revolutionary by any means, but I have to confess that it didn't occur to me that's a great per repo documentation reference tool or per folder.

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

#13

Bookmarks are something I have grown tired of. From the days of del.icio.us, I started collecting bookmarks and it kind of trickled along almost until Pinboard went on life support (or something else if you'd prefer to call that). The thing is - I just saved bookmarks, I never really utilised them ever, to find something, to go back to. I can remember once or twice and either I couldn't find anything among my bookmar…

I spend most of my days wading through the web. When i come across something that excites me I share the link to apple Notes. I dont write anything. Its just a bookmark. In February I spent a week sorting 5000 links into folders. It was quite satisfying to guess why i saved things, find patterns, create an organizational structure etc. the activity yielded both motivation and direction for my personal projects.

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

#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.

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

#16
post #5

I’m using a similar format to keep my links organized on an iPhone. A bookmarks.txt note kept in Apple Notes with markdown # headings to separate each category, allowing me to not keep open 500 tabs on Safari.

Why not just use actual bookmarks in Safari?

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

#17

Given that the aim is to still visit the URL, this appears to be browser bookmarks with extra steps. I am not seeing an advantage to the external storage mechanism and the overhead it brings. Browsers have been doing an excellent job of managing bookmarks, you can tag and search for them from the address bar itself which is very convenient.

Well, actually I could see a use for this in specific context and use cases, for instance if you happen to have different dev environments you're able to just move from machine to machine while keeping all the bookmarks in the repository. If you organise them you can even reference them from the codebase, or the documentation to avoid clutter. The format is simple and dumb enough so that a simple bookmark.txt can be…

we do something similar. IntelliJ (ultimate) has a text-based http client included. Like postman but you can commit .http files to the repo. Then this client has variables which can come from a json file. So basically all URLs that our software uses, are in that file. Eventually this led to the json file being used by scripts too.

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

#18
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

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

#19
I never really used browser bookmarks until I discovered Firefox's bookmark keyword feature [1]. It basically eliminates the search step. For example, I set "pr" to the GitHub pull request page. Just press Alt + D to focus the address bar, type the keyword, and hit Enter.

[1] https://support.mozilla.org/en-US/kb/bookmarks-firefox#w_how...

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

#20

Bookmarks are something I have grown tired of. From the days of del.icio.us, I started collecting bookmarks and it kind of trickled along almost until Pinboard went on life support (or something else if you'd prefer to call that). The thing is - I just saved bookmarks, I never really utilised them ever, to find something, to go back to. I can remember once or twice and either I couldn't find anything among my bookmar…

For some people, they have no need for bookmarks. For other people, bookmarks may be useful but the implementation is not.

Reading the author's description made me realize how unbookmark-like bookmarks actually are. The current implementations are somewhat akin to creating a list of books that you like at the library. It's not so much a pointer to the information you found useful, as it is a list of books you found useful. You still have to do some digging when you go back for the book. If the book is lost, you end up having a reference to something that you cannot obtain. And if you just add books to the end of your list, you still end up having to search through the list. The only way around that is to spend time organizing your list. It's no wonder why bookmarks are useless to so many people.

The author doesn't really solve the problem with bookmarks, except for one. The last one. By sticking a bookmarks file in a project directory, at least you're only searching through a list of bookmarks relevant to the project. If you are no longer interested in the project and delete it, you're also getting rid of bookmarks that you (hopefully) no longer need. It also addresses the portability of bookmarks. As far as I can tell, the only way to move bookmarks between any of the major browsers involves the use of special software or network services. Look at moving bookmarks from one Firefox installation to another: you either use online sync, export to HTML to import from HTML, or import the database (which replaces your current bookmarks with the ones being imported).

Post reply on HN