afuna_archive

I am resisting the urge to see how easy it would be to convert an extension, which works in FF2 but doesn't in FF3, to use Jetpack.

I had in mind Delicious Complete, as the only relatively simple non-FF3-compatible extension I'm aware of. It seems so easy, especially if I can just use the jQuery plugins!

Unfortunately (or fortunately), I find myself unable to decide how to include said plugins (I could copy and paste, or reference remotely using $.getScript, both of which have advantages and disadvantages, and I cannot decide!)

Resisting urge to code. Resistance weak. Maybe I should look through my extensions to see which ones say they're incompatible with the version of Firefox I'm using, and try rewriting the simpler ones out of curiosity.

I just found an alternative to Greasemonkey, called Chickenfoot. I think... it may abstract away some of the more technical language, and it is less sandboxed than Greasemonkey. So basically, more like an extension than a script. If that is true, I wonder how they stop malicious websites or scripts from gaining access? I'm curious; must set aside time (I don't actually have) to play.

I'm trying out Firefox 3(.0b3) right now! I decided to download it on a whim; I was hoping that it would be less of a memory hog than Firefox 2. Because trying to run that plus Aptana (Ruby IDE) at the same time was bogging down my system horribly. For the record, it seems to be running more smoothly, but the test may not be fair since most of my extensions were disabled for being incompatible *g*

I love the new features, including the improved downloads interface, additional interfaces (such as the new Applications item, which is the filetype-to-action mapping) and what look to be better error messages. One of my favorite things is that there is now a shortcut for the JavaScript console. It may not seem like much, but the inefficient way to open the JavaScript console has always been one of those little things that irritated me to no end.

It is somewhat strange to see the form controls be styled like Safari's. And the window is a darker gray than I'm used to. I am not enamoured, but I guess I'll get used to them.

There are a few rough spots; sometimes the rendering is weird and elements show up in the wrong place on the page (the header for Vertigo does this often on the Explore page). Also, the cmd+shift+T shortcut does not seem to always work; I often have to use the menu instead. I'm hoping that these kinks will be worked out by the time it makes it to release.

I'm excited about their moving the preferences storage backend to SQLite instead of writing to the textfile (prefs.js) only when closing the browser properly. I think this affects the values saved by Greasemonkey as well; if so, then that means I won't lose the data from the current session if the browser suddenly crashes. I am almost tempted to try to crash something so I can test :-)

I'm also excited about the improved search and bookmarking (with tags) functions -- searching through the address bar brings up results based on the address, the page title, bookmarks, bookmark tags, and I'm finding it pretty useful. (For example, when doing Support work, I can just type "entryprops" and get the URL I want, instead of having to type "livejournal.com/admi...", selecting whatever URL comes up, then deleting the end and triggering autocomplete again with "entr..."). There's also apparently auto-resume for downloads, though I have not tested it yet.

What should actually be showing up in that entry is the welcome video of OSX Leopard.

It's definitely not something being done by lj-toys, and I get the ad-filled page when I visit the page directly, so it's not just within the iframe. Somehow, Firefox is directing me to the wrong site/domain. But how? And why?

Not cache, because it persists after I clear and restart.
Not an extension, because I'm reproducing in an empty profile. Actually, for that reason, shouldn't be cache, either.

nslookup from my machine returns a different result versus the nslookup from ciaran_h's server. Plus, lj-toys works properly on Safari, but not on Firefox; I don't know why.

( nslookup results )

Fu: 0
That site: eleventy-one

Update:
Dre fixed it <3 Added a line to /etc/hosts, and now I have no problems. It's hacky, but it works. *purrs at Dre*