This Blog - Redesign

I'm doing massive re-write of the template. The site might be broken in the interim.

People who got here Googling for "A script from … was denied UniversalBrowserRead privileges": This has to do with Gecko's (the engine for Mozilla/Firefox/Netscape/etc. browsers) security policy. Scripts on webpages are prevented from doing certain things (like violating the user's privacy) unless the user concedes first to allow them. To establish this trust, the user must be sure the script is written by the author she trusts rather than for example by disreputable clients of the author's banner-ad provider. So it was decided the script's URL is not enough to establish its credentials, and the user should be guarded from trusting scripts based solely on their location. And thus the option to trust scripts was disabled by default. The only way the browser is even going to bother the user with "Do you really want to allow this bloke from perverts.de to virtually feel you up?" is if the script is electronically signed (this way you can be reasonably sure the script is written by whoever it says its author is). But my scripts aren't signed, so when they try to do something (I swear does not violate your privacy in any way, but of course I'd say that anyway) Gecko just slaps them on the wrist without consulting you and informs you as an afterthought ("that guy was so checking out your butt!").

If you want to tell Gecko you're a grownup and would like to choose your companions yourself, type "about:config" into your address bar, there filter for "signed.applets.codebase_principal_support" and change its value to "true" by double clicking it. This tells Gecko to ask you whether you let a scripts reach into your personal space or not, every time it tries.

More details from the horse's mouth are available here.

EDIT: A later template edit removed the client-side AJAX-based feedreader. It was a pioneering work, but it caused firefox to crash too much.