Doesn't seem to work at all on Chrome for Mac. Just seeing a single black line down the page.
It's fine for a test product to not support all browsers, but I think that at the very least, the most up-to-date version of each of the main vendors should be tested.
HN is refusing the GET requests now. I think they have a daily threshold set for queries. I'm troubleshooting options for working around this now. Most likely it will involve a cron job to pull entries on a set interval and saving those entries to the database instead of retrieving the entries in real-time when users visit the site
Off-topic but there is probably no good reason to use SRWare Iron: http://chromium.hybridsource.org/the-iron-scam.
Something might have changed after that was written but it doesn't seem very likely.
Benologist: Thanks! Unfortunately this site is just a (more attractive I hope) mirror of HN. Whatever HN allows to hit the front page will hit HN2.
To be clear: I'm not trying to steal HN's audience. I just think the folks at YCombinator have better things to do than to address UI issues and add new functionality. I'm trying to fill that gap with HN2.
Agreed. I plan to add comments over the next couple of days (once I get things working to the extent that HN will not block the GET requests due to traffic)
Next up: Handling sites gracefully that employ frame busting methods. I don't mind the ones that break out of the frame and redirect the visitor to their site - if they wish to do that, then that's fine by me.
What I need to figure out is how to best handle the sites that simply refuse to show their content. I'm thinking that, I should create a Javascript event that will just forward the user to that site (window.location = xxx) in the event that the site refuses to show content in an iframe. That way the user still gets to the content they want without interruption.
Does anyone have any feedback on that approach, or can anyone suggest a different one?
TZaman: I used an iframe because it was the only way of displaying the content I could think of without resorting to copyright infringement (i.e. doing a CURL query and reproducing the article on the site). If you can suggest a better and more user-friendly way, I'd be happy to consider it.
It's not the technology, it's just that I do not want a "preview" feature for every post on HN. When I see an interesting title, I click on it - otherwise I ignore it.
Update: Per PG's post at the location below, it looks like I can query once per minute safely. I'm going to do better than that and query once every 2 minutes. Hopefully a 2 minute delay won't be too much for HN readers to bear.
Congratulations Fizzadar! I think your refresh was the once that pushed the site over HN's limit :-)
I'm going to try using a different server to fact the data as a proxy which will then get stored to a database. I need to look around and see if HN has published any query limits so I can schedule the fact accordingly.
Thanks for looking and for your excellent feedback!
Thanks for the feedback everyone. It was working earlier - it looks like it hit some throttling threshold on HN due to the traffic. I will have to wait until the throttling period expires and then enable caching of requests.
You're the first one to report a back button issue. Can you give me details on what browser and OS you are using so I can try to duplicate the problem?
It's fine for a test product to not support all browsers, but I think that at the very least, the most up-to-date version of each of the main vendors should be tested.