This looks pretty promising. Judging from the demo, they have the UI close enough. They need to offer it as a service, though. I like that I have the freedom to run my own server, but I really don't want to have to bother in practice.
I like the decisions so far! On a pure style/preference note, I prefer content over chrome to an almost absurd degree - the margins around the individual posts could be tighter maybe?
Good old Java! Though I personally would never want what is suppose to be a slim low memory footprint application (reading text) to be ran by Java. But that's more of a personal objection, and has nothing to do with the actual product.
Okay interesting. But it currently doesn't seem to have all the bells and whistles for a local or a web client. Something tells me my memory usage will shot up if I attempt to import thousands of feeds into it. Besides, the fetching doesn't appear to be near the real-time (HN rss it pulled in for me, were at least an hour or more delayed).
Anyways, my installation on the windows went well. For now I'm back to testing InoReader.
Seems good, I like it. I might try it later on my server (hopefully it's not too heavy on the system, since I'm going to try it in a small vps).
But it's still another reader that I'll probably not use. Why? Because since there isn't an open standard for RSS reader I can't use it with the client I want.
I'm not saying it's your fault, as it sure isn't. But it's sad that we didn't learn this from the death of Google Reader. There were some talk about creating an open standard right after it's death, but nothing major came out of it.
This is also why I'm still using Google Reader, because every RSS reader out of there doesn't have either a mobile client or a website that I like. If there were an open standard, I could use the mobile client I want, the desktop client I want, and rely on the backend for synchronization and reading on computer without a desktop client.
This is true there isn't a standard for RSS feeds synchronizer, but Sismics Reader provide an open JSON API, so you can write whatever client you want, on any platform you prefer
This is great, but every developer has to include your API to get it's app working with your service. And he has to do it for every service that he want to support (Feedly, FeedBin, Feever, NewsBlur...).
My rant was not about Sismics not providing an API, but the lack of a standard open API for RSS readers. Beside that, Sismics seems pretty great.
My initial thought was a portable version of this could be useful... I don't use thunderbird much these days, but for several years had my tbird profile symlinked to a dropbox directory. The only irritation was the notices from dropbox if I accidentally left tbird open at another location.
I imagine the same or similar could work here too.
I wasn't able to get Liferea to work with TTRSS, and I really tried :-/. Therefor I wrote one myself but it has only the possibility to show posts, no list or anything because I never used that http://jabs.nu/feedthemonkey I assume most of the people will not be comfortable with it.
I deployed TTRSS to Azure pretty easily, although auto-refreshing the feeds is harder to figure out. The Web UI seemed good enough. Not as easy as Google Reader but serviceable.
A Google Reader replacement for me is some sync-server with which I can sync read/unread between a native feed reader on my iPhone, my ThinkPad, my Android tablet and my iMac.
With all the cloud DBs available... one would think you could simply target one of them as a platform (say mongodb) and that you could define a set of collections/tables/account to use. You could get quite a bit of data in a free account level with couchbase or mongolab. You wouldn't even need to store the full article, just the feeds, urls, dtm and read status... you could do more, but it could work.
For that matter, one could come up with such a "MyData" system that works with the DropBox API or something similar.
I would like just a protocol for which I or basically anyone could implement a server and a client, kind of like SMTP and IMAP for email (but as a REST service or something easier)
And as soon as Reeder (iOS/Mac), Press (Android), gReader (Android) and whatever Windows people use agree on a common API and all support adding your own server URL, then it will be possible.
The problem is that all of the clients seem to want to hitch up with another free 3rd party service :(
Yeah I hoped someone would come up with such a protocol, I myself been writing about that last year already, but sadly 3rd party service it seems to become.
49 comments
[ 2.8 ms ] story [ 102 ms ] thread[1]: http://feedhq.org/
Unread view, one unread post: https://dl.dropboxusercontent.com/u/611024/feedhq/Screen%20S...
Post view: https://dl.dropboxusercontent.com/u/611024/feedhq/Screen%20S...
[edit: moved files in my dropbox]
wheezy/sid (Really Mint Linux but whatever)
openjdk-7-jre:i386
$ sudo dpkg -i reader-1.1.1.deb
dpkg: error processing reader-1.1.1.deb (--install):
parsing file '/var/lib/dpkg/tmp.ci/control' near line 2 package 'reader':
error in Version string '${reader.version}': version number does not start with digit
Errors were encountered while processing: reader-1.1.1.deb
Hope that helps.
[Edit]: Also, keyboard shortcuts (most important for me: jk for next/previous).
Anyways, my installation on the windows went well. For now I'm back to testing InoReader.
But it's still another reader that I'll probably not use. Why? Because since there isn't an open standard for RSS reader I can't use it with the client I want.
I'm not saying it's your fault, as it sure isn't. But it's sad that we didn't learn this from the death of Google Reader. There were some talk about creating an open standard right after it's death, but nothing major came out of it.
This is also why I'm still using Google Reader, because every RSS reader out of there doesn't have either a mobile client or a website that I like. If there were an open standard, I could use the mobile client I want, the desktop client I want, and rely on the backend for synchronization and reading on computer without a desktop client.
My rant was not about Sismics not providing an API, but the lack of a standard open API for RSS readers. Beside that, Sismics seems pretty great.
https://news.ycombinator.com/item?id=5947276
feeds are synced by the server
I imagine the same or similar could work here too.
* https://wiki.merproject.org/wiki/Nemo
* https://sailfishos.org/
I deployed TTRSS to Azure pretty easily, although auto-refreshing the feeds is harder to figure out. The Web UI seemed good enough. Not as easy as Google Reader but serviceable.
Importing my feeds works for 5 of them for a short while, after getting the items for the 5th feed it reverts to thinking I have no feeds at all.
However - pull request.
For that matter, one could come up with such a "MyData" system that works with the DropBox API or something similar.
The problem is that all of the clients seem to want to hitch up with another free 3rd party service :(
/uninstall