Sorry, but not terribly surprised, to see FeedLounge shutting it’s doors for good. It’s a shame, there was a lot of really great stuff in FeedLounge.
Sorry, but not terribly surprised, to see FeedLounge shutting it’s doors for good. It’s a shame, there was a lot of really great stuff in FeedLounge.
You know, it might be interesting to see the backend, were no one to pick up the reins. Hint hint
. Just saying.
Don’t hint to me, I haven’t been part of the team for a while now.
Sad to see it happen, but I too am not surprised. I left FL a while back after you left and things seemed to stop working. FL had by far, the best potential of any web-based feed reader, but the bugs and issues were too numerous. I truely hope someone can pick of the pieces and revivie it as it was the best while it lasted.
Sadly I think the only logical option would be to opensource the project. For everyone to use on their own server and help contribute to fix the bugs and increase the overall functionality. Then if Scott wants to host feedlounge it could be ad supported or a paid hosted service.
I remember the days when fl had so much of my attention. Like Chris after you left it lost it’s appeal and GR launched it’s new UI.
[...] hearing I commented on Alex’s site: Sadly I think the only logical option would be to opensource the project. For everyone to use on [...]
Like I said, what happens to the FeedLounge code now isn’t my call. However, last I saw it I’d say it is extremely unsuitable for running as a self-hosted installation.
One of the earlier versions might be suitable, where only one database was used (back when FL was MySQL). The current distributed architecture is way too fat for a single user install, IMHO.
Wow, I’m sorry to see it go. I had a great time working on it and will have a hard time settling with a different reader. what about a SQLite version…?