4 ms·
Bookmark managers should happen in the browser, not in the command line. I recommend Shaarli: http://sebsauvage.net/wiki/doku.php?id=php:shaarli http://sebsauv
by subbz 9y ago
Bookmark managers should happen in the browser, not in the command line.
I recommend Shaarli: http://sebsauvage.net/wiki/doku.php?id=php:shaarli http://sebsauvage.net/wiki/doku.php?id=php:shaarli
- apjana 9y agoAuthor of Buku here. In fact Buku can store bookmarks directly from the browser. You have 2 ways to do that (including a dedicated plugin). It also has 5 different search options with a powerful prompt to find out just any bookmark you have stored (we have users who imported even ~40K bookmarks from Delicious and are happy with Buku), extensive flexibility of editing and manipulation, encryption support, multithreaded full DB refresh and a lot more. In addition, Buku is also developed as a library and Shaarli can use it as a powerful python backend over REST. ;) Yes, one of our contributors did want to add a feature to generate a full webpage with thumbnails but we decided not to add it as it seemed simply ornamental when you think about the raw potential of Buku.
- apjana 9y agoOh and one more thing about Buku... it is designed to simplify your workflow beyond imagination. You search something in Shaarli, get 10 results. You want to open results 4, 5,6,7 and 8. What do you do? Click 5 times? Not with Buku. You enter: o 4-8 terminal bliss, yeah!
- a3n 9y ago> Bookmark managers should happen in the browser, not in the command line. Really? Why? I would much rather my browsers were clients of a bookmarks server/api, and what happens/seen in one browser is exactly the same in all. I use different email clients, and thank $GOD that they all consume IMAP instead of email storage "happening in the client."