Any chance you could just store the images in a single local image and use CSS sprites, instead of loading favicons from every different site. The front page does 62 HTTP requests and they're all over the place...
I could do, but the way it's built is using a master array in the page creator file. To add a feed, I just add the new feed and favicon location into the array. Storing the images would mean more work each time a new feed is added.
Having said that, CSS Sprites is something I don't know much about and will be looking into.
It'd take a tiny bit more work on the frontend, but instead of saving the favicon location, you could save a data-uri of the favicon image. That would then completely eliminate all of the external HTTP requests.
The Next Web added, should show on the next db refresh.
Plans is an interesting question, thanks for asking.
When I built it originally I had this huge project in mind (as we all do :) ), bookmarks, saved articles in a user area, FB login, link tracking for a "most popular links box", live stream, recommendation algos, the works.
I guess this scale is one of the reasons I originally dropped it.
After the rediscovery I thought "let's go MVP on this". So I cut everything back. What you see is what surivived. Literally, just the news links, on a html page, that is quick to load with no server hit.
Future plans - let's see how it goes eh. If the hosting bill enters the trips I'll drop a few ads in, but I like the cleanness of it all for now.
