Hacker News Reader

Comment by jenoer | Hacker News Reader

It's not perfect yet since it uses jQuery instead of pure JavaScript, but: This is my first (tiny) project in over a year. I was inspired by a HN post I saw some weeks ago and thought I'd share this with others since I'm quite proud of how well it's working.

This also gave me the inspiration of focussing on learning how to code. This will be a very useful skill since I'm a software tester for a PHP (and JavaScript) based web application.

(I am yet to add it to the Chrome Extensions, but Google asks 5$ which isn't a lot, but they only allow Credit Card, so this will be on hold until I aquire one.)

View on HN

Thanks for releasing this, but it would work only properly (and be more efficient) if you checked for window.opener directly in new documents instead, and simply set it to null before document scripts are run (using the beforescriptexecute event is one option).

I do the same using a "@run-at document-start" userscript, but I'd be glad if I could point people to a proper firefox extension.

That's a very good point, thanks for sharing!

I will take a look into this because this sounds very interesting. I am new to "this" though, so it will take me some time to figure out how to implement this into, perhaps, a v2.0, but I'm surely taking up the challenge to learn more about this, so thank you for the tip!

Mildly related, but since when google asks for money to release extensions? Is this a joke?

Unfortunately not. Once you set everything up to Publish the extension and hit the Publish button, Google informs you need to pay a 5 USD developer registration fee (using Google Payments) which allows you to publish up to 20 items.

Edit: They claim this is "to check the legitimacy of the accounts of the developer to ensure users are protected against fraud." (paraphrasing slighty)

I only use chromium (not even chrome!) for testing, but as an OSS developer I'm even more appalled by this.

When I polished the extension with a custom Icon, I went to the Chrome Store with a big smile on my face, it asked me to set up settings, let me set up a custom icon, forced me to think of a good informational text, and at the "moment supreme" of hitting the Publish button it asked me for a credit card. Luckily Mozilla returned that smile and had a suprisingly fast review-proces, it only took around 12 hours I think.

Anyway, now I can first see how popular it will be on Firefox before I decide to try find a 'throw away' credit card.

Reply on news.ycombinator.com