|
@@ -13,7 +13,7 @@ Goals:
|
|
|
- supports tags and descriptions, too
|
|
|
- one file per bookmark
|
|
|
- CLI-first
|
|
|
- * but having a GUI would be nice, too
|
|
|
+ * but support
|
|
|
- python3
|
|
|
|
|
|
|
|
@@ -94,6 +94,63 @@ mxb mv coding/python/exercises/dfkljedua work/todo/
|
|
|
xsel -b | mxb add
|
|
|
```
|
|
|
|
|
|
+Why
|
|
|
+========
|
|
|
+
|
|
|
+Are bookmarks abandoned?
|
|
|
+-------------------------
|
|
|
+
|
|
|
+### Low development
|
|
|
+
|
|
|
+Web browsers get tons of features in the recent years. In my opinion, they still suck at bookmarks. They
|
|
|
+barely do what they used to do in the early 2000's.
|
|
|
+Sure, most browsers added _tags_ to bookmarks: but you can't search them in the bookmarks menu. At least in
|
|
|
+firefox, you can in the location bar, sure, but that looks messy to me: when something doesn't show up, it
|
|
|
+doesn't mean there isn't. Sometimes FF "logic" just hides that link to my view.
|
|
|
+
|
|
|
+### Low modularity
|
|
|
+
|
|
|
+No browser is making any effort to make its bookmark system useful even when the browser is closed. There are
|
|
|
+so many reasons why that would be useful:
|
|
|
+ - having scripts to import/export
|
|
|
+ - sync with other browsers
|
|
|
+ - scripts that check for links that are nowadays non functional, dead, page not found, etc and clean the
|
|
|
+ bookmark store
|
|
|
+
|
|
|
+So we're stuck following every change to FF internal method of using that database, and adapt our scripts.
|
|
|
+
|
|
|
+### Practical use cases that suck
|
|
|
+
|
|
|
+ - moving bookmarks from one profile to the other?
|
|
|
+ - moving a single folder to another profile or browser
|
|
|
+ - export
|
|
|
+ - concurrent access (firefox keeps `places.sqlite` open, so it's locked)
|
|
|
+ - synchronization using already available tools (Firefox Sync started as something really cool and became
|
|
|
+ something horrible)
|
|
|
+ - using multiple browsers, but a single bookmark store
|
|
|
+
|
|
|
+### My take on it
|
|
|
+
|
|
|
+Bookmarks are abandoned to the point of being killed. Apparently, the new paradigm is the search: you can
|
|
|
+bookmark stuff, but you aren't really intended to browse bookmarks later. You can try to retrieve them using
|
|
|
+the location bar obscure mechanism of giving you what you might need.
|
|
|
+
|
|
|
+I think this approach is flawed: it doesn't give the user much control over its notes, so he/her needs to
|
|
|
+delegate to some form of "artificial intelligence".
|
|
|
+
|
|
|
+Why not any of the existing solutions?
|
|
|
+--------------------------------------
|
|
|
+
|
|
|
+I'm not the only one to complain about it, so there are very nice tools: `buku` and `bm`, to name just two of
|
|
|
+them.
|
|
|
+
|
|
|
+I think their approach is on the right track! However, I don't like having single-file SQL databases. They
|
|
|
+will share some of the issues that most browsers implementations have:
|
|
|
+ - concurrent access
|
|
|
+ - synchronization using already available tools
|
|
|
+
|
|
|
+So I'm trying to do a similar job, but using a storage that is simpler and more versatile.
|
|
|
+
|
|
|
TODO
|
|
|
=========
|
|
|
|
|
@@ -103,3 +160,4 @@ TODO
|
|
|
- helper:
|
|
|
- write a marxbook-search helper based on peco
|
|
|
|
|
|
+
|