News for hackers. Stuff that matters.

Jendib

I made this project in my free time a few years ago, to organize my own documents, and then decided to use my newly created company (2 guys) to make a real product out of it.

There is a self-hostable version on Github also (Docker image working out of the box).

The server part is made in Java with an embedded H2 database and a Lucene index, and the frontend is mostly AngularJS.

Feel free to try out the demo and give me some feedbacks!

I'm the main developer, feel free to ask any question, I'll be happy to answer!
Re:An open source Google Reader replacement: Sismics Reader on Wednesday June 26, 2013 @12:58PM (#5947290)
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
Re:An open source Google Reader replacement: Sismics Reader on Wednesday June 26, 2013 @12:56PM (#5947281)
Of course they are :)
Re:An open source Google Reader replacement: Sismics Reader on Wednesday June 26, 2013 @12:56PM (#5947276)
The feeds are remotely synchronized on the server, so you will see the same since whatever your client is (mobile or desktop)
Re:An open source Google Reader replacement: Sismics Reader on Wednesday June 26, 2013 @12:55PM (#5947269)
We use CSS media queries to adapt the UI with the screen size
Re:An open source Google Reader replacement: Sismics Reader on Wednesday June 26, 2013 @12:55PM (#5947262)
Keyboard shortcuts should be in the next release (there is an issue about it on GitHub)
Re:An open source Google Reader replacement: Sismics Reader on Wednesday June 26, 2013 @12:54PM (#5947254)
Sure, there is a theming system, so you can fully customize the CSS
Re:An open source Google Reader replacement: Sismics Reader on Wednesday June 26, 2013 @12:53PM (#5947250)
Thank you, I have just fix the issue on Debian packaging
Re:An open source Google Reader replacement: Sismics Reader on Wednesday June 26, 2013 @12:52PM (#5947240)
Hi, I'm one of the 2 developers, can you add an issue on GitHub and join your XML, so we can fix this?