Hey Maciej, just wondering. Does having this link on the HN frontpage influence the amount of new subscribers you have today, and possibly tomorrow? Just curious
It's far from perfect, for instance how do I access my bookmarks while offline ?
from the original shaarli FAQ:
What use Shaarli and not Delicious/Diigo ?
With Shaarli:
The data is yours: It's hosted on your server.
Never fear of having your data locked-in.
Never fear to have your data sold to third party.
Your private links are not hosted on a third party server.
You are not tracked by browser addons (like Diigo does)
You can change the look and feel of the pages if you want.
You can change the behaviour of the program.
It's magnitude faster than most bookmarking services.
I switched to shaarli back in the days when del.icio.us was bought by yahoo. I am using it ever since without problem. Hosting on super cheap PHP hosting. The open-source community took over the project from original author and they are maintaining it. Highly recommend.
Going with something like sqlite is not always better -- if what it provides is not needed, it's complexity for complexity's sake. PHP arrays are perfectly fine (until you reach a certain size), particularly when using a direct key access scheme. Loading/saving the data is pretty much a file_get_contents|file_put_contents affair, with some inline filters such as serialize & gzip. Couldn't be simpler, and it sounds like it doesn't need to be more complex than that.
Wallabag seems designed to mimic Pocket more - but I'm only basing this on a quick glance. Can anyone cite any pros/cons of each platform? For example is one better to host on a smaller vps? (My use-case is really minimal, just personal bookmarking, not a team or anything like that.)
Shaarli is a tool to bookmark, tag, comment, publish on links you want to keep.
Wallabag is a tool to save content to read later, it makes a local copy of the relevant content which it displays with usually improved readability and save content from linkrot, once read you can either save it, push it to your shaarli or delete it.
I chose to self host both on a shared webserver and they require very little effort for installation and maintenance. Some link are not wallabag friendly and once in a while it will fail to retrieve content, there's a button to report the link to wallabag dev so they can improve the situation and a button to go to the original link destination.
I never used pocket, this is a third party closed source service which is the opposite way of how internet is supposed to be done.
If you cannot afford or do not want a shared hosting, you can host this locally in a virtual machine.
Do browsing this page feel slow ? Try browsing older pages, too.
It's not slow at all, is it ? And don't forget the database contains more than 16000 links, and it's on a shared host, with 32000 visitors/day for my website alone. And it's still damn fast. Why ?
The data file is only 3.7 Mb. It's read 99% of the time, and is probably already in the operation system disk cache. So generating a page involves no I/O at all most of the time.
The crucial distinction as far as the OP is using the term seems to be that such a datastore does not require the user's hosting provider to give them an instance of any of the common DB servers, which typically needs a more expensive plan than the usual baseline of "disk space and an httpd [that supports calling out to one or two scripting languages]".
(Basically it should run on anything more complex than a static site host. Though it's also true that sqlite would probably be a cleaner choice for the datastore without losing any of that benefit.)
SQLite would be nowhere near the current design in term of performance. Typical shaarli usage involve little update (a dozen a day maximum) an a lot of read (10k+ pages viewed per day on sebsauvage's instance (shaarli's creator, an influent french blogger). Thé file system's cache works really well in this kind of scenario, way better than SQLite.
For the stability guarantees, shaarli exists since 2011 and is used in production by many (several hundred) people without trouble.
I'm a long time shaarli user and the reason I use shaarli is to get away from services such as yours. I trusted del.icio.us got bitten and will never make the same mistake again.
paperbin.co is useless and pointless to me, it is contrary to how the internet and the web is supposed to work, it is closed source crippleware with no possibility to self host, it offers no features that has not been around in competitors for years.
This is a reason why I ignore your project but am excited to participate in discussion about shaarli and wallabag.
Be nice to see something that uses cloud storage like Azure table storage, but run locally so at least I have a backup. Also that log is horrendous, but hey its free!
The "datastore" is a gzip+base64-encoded serialized PHP object written to a file.
It's really efficient under shaarli's typical workload : really few writes ans a lot of read => almost no IO, everything stays in the filesystem's cache.