Hey there,

I'm one of the earliest users of Delicious who recently built a modern bookmarking platform. It's called Kozmos (https://getkozmos.com). It's a competitor to Pinboard, and its difference is simplifying bookmarking into one heart button, I mean you don't need to fill forms to bookmark a page anymore. It has an advanced search engine that makes you find whatever you're looking for.

I self-funded this project and worked on it past three months. If you are curious about how it looks, you can see this blog post; https://medium.com/@azerbike/introducing-kozmos-a-new-bookma...

My vision for this project is to not just build a bookmarking platform, to innovate further based on bookmarking.

Looks cool. And I was thinking about how a better experience to bookmark could reshape how I use the browser now. Funny how coincidently you went from building a better browser to build a bookmarker. Btw, I used to use Too-Many-Tabs to change from House to Work mode. Now I have 2 logins on Chrome, is there anything like this on kozmos?

Yes, so glad other people also see what I see. Bookmarking is like the missing piece of current web.

I don't have that feature in Kozmos but will keep it in my mind.

Personally, I absolutely need the option to tag bookmarks, is this supported, or do you have plans to?

I imagine pinboard supports this, but when I looked at it something stopped me from pulling the trigger, despite how desperate I am for this type of service.

Kozmos will support collections soon. So users will be able to organize and publish their links.

For tagging, it has a different approach. It has tags behind the scenes; reads the tags from the bookmarked page, and adds also additional tags such as the type of content.

A collection would be like one tag I suspect. And auto tagging is not what I'm looking for that's for sure.

Hey Azer! Was wondering what you've been up to, I couldn't remember what your name was, always be #leftpadgate guy to me. Gonna check out your service.

Let me know what you think!

This looks nicely executed with some fresh ideas. Good luck!

thanks!

Curious to know, what's your business model? You mention you self-funded, but is the intention to have paid accounts, sell advertising, etc?

The business model relies on the next versions which will introduce new innovative ideas on top of bookmarking. It'll take some time, I won't rush. Currently the server is AWS free tier so it's not costing me anything. Personally I'm doing contractor to keep my budget healthy.

Having a business model will get you more users. I'd add it sooner than later.

I do have a business model, but not for this version of the app

Fermat's last business model

I hear you.

I used Pinboard a couple of years ago but stopped using it in favor of Pocket (I can't seem to recollect the exact reason why). Pocket is great for things that I want to save for later. I have cached copies of webpages in my Pocket that are no longer online, so that is pretty neat.

Lately I've noticed that Pocket has become like a cold storage for me. I rarely ever go back to reading the bookmarks from it. I recently found a bookmarklet [1] on PH that works like Pocket but sends the bookmarks to your email instead of sending it another app. It has been working pretty well for me so far. I've been using it to send myself an email for stuff that I want to read in the near future (within the next couple of days or so) and use Pocket for saving links that I might need at some later date.

But discoverability is still an issue, I am yet to find a decent solution that can help me find new things based on my interests.

[1] https://www.emailthis.me

I've discovered that the missing link for me was getting the articles onto my Kindle. I now read between 100-150 articles a month this way, previously I would read only 10-30 articles in a month.

I use Wallabag, an open source alternative to Pocket. It generates an RSS feed which Calibre can read, download, and send to the e-reader. Pocket should do the same thing. Once a week or so I go through and mark articles as read, then open up Calibre to re-download the fresh feed.

One weird trick (heh) that has become really useful is reversing the RSS feed. So I receive two 'e-books' on my Kindle, one with new articles and one with old articles. This satisfies me, since I'm often wanting to read some new articles ASAP, while also working my way through the backlog.

Calibre lets you script the feed processing in Python. With Wallabag the feed is also paginated, so you could accomplish nearly the same thing by selecting a higher page number. Not sure if Pocket does that.

Came here to also suggest wallabag. Getting running on your own host is dead simple (just a few 'apt-get's and a 'make' script) and the community has made apps for just about every platform. Also, as a limited-vision reader, the accessibility options are really well done!

I was looking for a pocket replacement due to privacy concerns and an ever growing annoyance with ads. Wallabag has a Pocket importer and the rss feeds are a really nice touch! I even put up a parser on my website to show people my starred articles: http://desandoval.net/i-am

I'll try the ebook trick. That is a really good idea! I was looking for a reason to pull out my old B&N Nook again ;)

First I used browser bookmarks. Organizing and searching them was a mess. And link rot was terrible.

I looked for something different and used OneNote to store complete web-pages in the cloud. Link rot was gone and organizing and searching was awesome. Until my OneNote file on OneDrive reached 8GB and performance and syncing took a nosedive.

And not so long ago I found ScrapBook for Firefox [1]. Couldn't be happier! Storing everything locally is awesome. Searching and organizing full pages and links is great. I can take care of backing up the data myself and can crawl the pages on my local drive.

I just hope that firefox keeps those plugins running, otherwise I'll have to find something else again...

[1] https://addons.mozilla.org/en-US/firefox/addon/scrapbook/

I have used https://www.icyte.com/ for years to combat link rot (disclaimer: I am currently the maintainer of the site).

My current favourite tool is this chrome extension(https://chrome.google.com/webstore/detail/save-to-google-dri...), which saves pages in mht format to google drive.

Thanks for your input. But there are a few important things which I really like about ScrapBook:

It's simple to organize. A sidebar with folders, supporting drag and drop.

It stores the source 'as is' with html, css, images and optionally js. This simplifies tooling and scraping locally. Afaik, MHT is not yet fully supported on all browsers.

I can go offline and look at stored pages. This is very important for me because I have a long commute by train each day.

Since OneNote I avoid cloud storage and syncing when possible. After GB's of Data, syncing starts to be a nightmare. But, I could start syncing with dropbox, rsync or something else. And I'm free to choose. Fortunately I don't need collaboration features.

In my opinion a simple, local solution beats everything else. Actually, a feature like this should be built into the browser natively. And it's not far off from the current state: It is simply a bookmark sidebar which also supports save-page. It's kinda sad that, after so many years, browser still make it hard to store and watch content offline. The current save-page functions just don't cut it.

The most important reason I continue to use Pinboard is that it's the only service I'm confident won't be acquired and shut down within a week with no warning or no data export. (based on Maciej and his talks, blog posts, etc.)

The rest of the services mentioned in this thread? Who knows?

Try Are.na (https://www.are.na). Built for saving all types of content, more centered around organizing information than straight-up social bookmarking (though people use it to do that). Disclaimer: one of the co-founders.

Out of curiosity, why is Pinboard "not for you"?

The experience I had using pinboard was very similar to what I have using Chrome and Firefox Bookmakers. As I said, I still have saved pages I used in 1996, I have never had an experience of losing everything. So, the only advantage would be the rankings and the tags trends.

Well, and being able to get at your bookmarks from anywhere, and being able to attach searchable descriptions/tags to the bookmarks so you can find it even if the page title or URL isn't memorable.

Firefox bookmarks support tags, keywords and descriptions. Plus it syncs (encrypted end-to-end), so you can get them anywhere if you can use Firefox from that place.

I didn't realize any browser's built-in bookmarks supported tags and descriptions. That's neat.

I use both browser bookmarks (Firefox) and Pinboard. I think they're complementary rather than one being a replacement for the other.

I use browser bookmarks for pages I visit often or intend to return to fairly soon. I use Pinboard for long-term archival where link rot is a real concern.

It's not really what you're after, but we're some folks trying to compete with Pinboard. I'm sure Maciej once tweeted something about it being a business that could be successful for a couple of indie devs, not a big VC-backed startup, and that's what we are... Although the successful part is still a ways off :)

Anyway, our thing is https://larder.io. Our angle is that we'll sync your github starred repos as bookmarks along with everything else you save.

What if the Web were filesystem-accessible?

https://www.reddit.com/r/dredmorbius/comments/6bgowu/what_if...

There are some neat features described, but I don't see them to have much to do with the filesystem accessibility. I can see the advantages of using a standard interface for many kinds of sites, like social media, but the filesystem format is neither necessary nor sufficient for that (since it says nothing about the format of the actual files).

A filesystem is an abstraction to an information store which removes the underlying implementation details of accessing that store.

A filesystem is a CRUD (or BREAD) tool, based on standard metadata and interfaces. Part of that is making available extra and user-useful capabilities.

Another part of the problem is that the current concept of a browser, which lacks the idea of downloading-and-storing, on an accessible and persistent basis, online content, and emphasises application and interactive functions over document and reference capabilities, is ... something of a historical accident.

Why make use of some remote pinboarding or bookmarking feature if you've got a common URL referencing system, and the ability to capture, transform, rate/rank, search, and organise into a workflow, project, or support context the information you're accessing via the Web.

And to do that by way of tools which treat this as information-on-disk, either known and extant utilities, or extensions / wrappers / enhancements of these. Most specifically, by unwrapping online content from the browser context specifically.

This goes deep into principles of application, information, and interface design and use. I'm calling the extant model a dead duck.

I agree with your diagnosis of browsers and with the idea of using local tools that interact using standard CRUD interfaces, I just don't see the filesystem part buying you anything over HTTP, which provides all that. I think it's a useless distraction at best, and a fatal flaw at worst.

I also disagree that the app-ification was an historical accident; I think it's the direct result of economical forces, and I'm not convinced that an alternative system could become popular while avoiding it.

Economics forces shape historic accidents too. That's very much part of my model.

You might want to look through the inspirations part of the doc to see what's prompted this. I've also turned up a number of similar projects after having started writing that essay.

But:

* The /proc and /sys filesystems on Linux

* The /net virtual filesystem on many Solaris systems, generally tying to an NFS network via automount.

* Various Plan 9 elements, including /webfs

* The Midnight Commander virtual filesystems, including remote access over ssh.

* SSHFS.

* Tools for on-demand and responsive media response. Tracking an element down to its source, and requesting, say, PDF or ePub rather than HTML might automatically provide those. The idea of being able to run, say, 'ls' on an HTML target and have it return a list of links rather than its full content.

* Unix mail, mailx, mutt, and especially mh, which provides a shell-based perspective to email management.

* Numerous document markup and preparation systems.

* Squid, dansguardian, Tor, and other Web proxy tools.

* Libraries and catalogs, generally.

* The Internet Archive.

* HTML doc "reader-mode" tools: Readability, Pocket, Instapaper, Outline.

* Search

Again: wiring much of this into the FS layer, abstracting away the browser, treating doc requests as queues, splitting up docs, media, apps, and commerce, integrating into the user's workflow rather than the publishers.

If it's not for you, that's fine. But that's where I'm coming from.

I can relate to a lot of your sentiments.

I'd like to share a project I've been working on, https://slushi.es

Tried Toby?