Mozilla Japan's Mascot, a little "firefox" named Foxkeh, became popular across the Japanese speaking Internet quite quickly and wherever he goes, people seem to like the cute little fellow.

I personally always liked his monthly wallpapers (featuring foxkeh and the current calendar), though admittedly I wasn't quite able to read Foxkeh's Japanese blog.

As of today though, Foxkeh has an English blog as well, foxkeh.com, and you should check it out.

After all, you are as curious to learn new things about the web and Firefox as Foxkeh is, aren't you?

Read more…

The newly released Thunderbird 2 was promptly BoingBoinged: Cory Doctorow calls Thunderbird "free, kick-ass email" and shows that Thunderbird is the best mailer out there, for the average and not-so-average mail user:

I send several hundred emails a day and receive at least a thousand non-spams every day. I need an industrial-strength mailer, and I get it from Thunderbird. I love it.

Thanks to Cory for the nice review and thumbs up to the Thunderbird team for their latest and greatest release :)

Read more…

I just stumbled across this list of company name etymologies on Wikipedia and noticed that Mozilla is also on there. It reads:

from the name of the web browser that preceded Netscape Navigator. When Marc Andreesen, co-founder of Netscape, created a browser to replace the Mosaic browser, it was internally named Mozilla (Mosaic-Killer, Godzilla) by Jamie Zawinski.

Mozilla, the Mosaic-Killer. Funny. (Even though I can't quite say much about the historical accuracy, of course).

(via kottke)

Read more…

I linked to this blog before, but now there are 15 common American prejudices about Germany on there that you might want to read.

It's funny how right the author is. And don't worry, you shouldn't feel bad if you get disillusioned about some totally bogus things -- because quite a handful of them are also dead on. And haven't you always wanted to know which ones are which?

By the way: Happy Easter holiday everybody. Don't feel too bad that we also have Monday off here :)

Read more…

Alright, my bags are packed and I am about to leave... tomorrow morning. Rumor has it it's snowy in Germany which feels kind of unreal considering how sunny the Bay Area is at the moment.

Just so I know what's expecting me in Germany (in case I forgot), Jean Pierre sent me a link to 20 things to keep in mind when visiting Germany, a quite funny list of things you might (well, you will) stumble across when you make it to my home country.

Things I am looking forward to? The food. The beer, obviously. Spring and summer. Some of my classes. Making more music again (my trumpet really does want to get played more often than recently!). German folk festivals. That the price on the shelves is actually what I have to pay. The metric system. Buildings with walls that actually deserve the name. Public transportation that works. The autobahn and people who know how to drive stick (no offense ;) ).

Things I am not looking forward to? The cold weather! Some of my classes! Gas prices. Closed stores on Sundays. Bad customer service, at times. Kind of a shortage on the "free wifi" front. Dubbed TV shows. 19 % sales tax.

As you see, I am all set -- except for that "proud to be an American" t-shirt morgamic wanted to get me, of course :) Cheers!

(The picture is CC-licensed by caribb on flickr, and it's purely symbolic: my plane(s) are not even going to be Airbuses)

Read more…

I really like this recent Mozilla poster:

(As far as I know) it first came up as a concept (see below) at the Firefox on-site meeting in Mountain View in November 2006, and because it's pretty irresistibly cute, we really couldn't let it catch dust in a drawer :)

Fligtar caught the presentation slide at the Firefox summit:

Good job, Dave and the rest of the marketing team!

Read more…

Friday is approaching fast. It'll be my last day as an intern with the Mozilla Corporation!

It was a fun and exciting time, and I learned a lot. Six months long, I was working full-time on the Remora (addons.mozilla.org version 3) project, and during my journey through the complete software development lifecycle I got to tackle quite a few tricky issues that turned out to require new and unique solutions that I really enjoyed inventing and implementing (to use morgamic's recent words: "things you can't google for"), and I am proud that part of all this now carries my signature (if you are interested, at the moment, that's something like 60.000 lines of code svn blames on me).

Yet for now, I have to go back to school and finish up my degree: After all, I want to become a "Diplom-Informationswirt" (that is, a Master's Degree in Information Engineering and Management), and that'll take me pretty much another four semesters.

I want to thank my fellow AMO web devs (morgamic, clouserw, shaver, sancus, fligtar and Cameron) for their (ongoing) work on the project, their efforts to get me integrated into the project and Mozilla in no time, and their constant valuable input on my work. Thanks to schrep, Mitchell, John and cbeard who did their very best to help me get the most out of my internship. Thanks to all the other employees who sparked my inspiration and expanded my horizons time and again in interesting conversations, presentations, etc. Thanks to dolske and faaborg who I never regretted to share a "cube" with. And last but not least to the countless others all over the Mozilla community who I got in contact with (and there were a lot!).

That being said, I'm not out of your hair yet ;)! Even after my return to the college campus, I'll stay on the Mozilla webdev team, and I'll keep contributing to Remora and other projects to come; only I'll be on IRC at slightly different times of day...

See you in Europe!

Read more…

When I just closed Firefox (on OSX), I got this window:

Firefox -- New Settings New Settings have been created for this application. Do you wish to use these settings from now on? [Use new settings] [Use original settings]

Quite frankly, I am confused. Now I don't know if this is a Firefox window or one that the OS gave me, but since I upgraded to OSX 10.4.9 earlier today, it is possibly something OSX asked me. Yet, I have a few thoughts on this, if you ask me, unfortunately bad piece of UI.

1. May I see your ID please? Who are you, after all? Not only did the window itself not have a title in the title bar, also the menu bar was completely empty. I had no idea whatsoever, what process/entity/program asked me this question. I actually still don't know. Let alone...
2. ... why? As a basic rule of thumb, I expect dialog windows to tell me, at least, why they they showed up in the first place. "New settings have been created" is fairly vague. What kind of settings? Who created them? And why do I have to make a decision? But worst of all...
3. ... what will happen? Now that I don't know what the decision is even about, I am even worse off since I don't know the implications of either of the decisions. If I click "new settings", will you overwrite my Firefox profile? Will I lose data? What will change, compared to how it was before? Or, if I click "old settings", (still assuming the window has a reason to show up in the first place:) will that make my Firefox instance unusable/incompatible with some sort of magic and important component?

I clicked "Use new settings", and, judging by the fact that I can still blog, that doesn't seem to have been the "wrong" decision. But you never know...

Thoughts?

Update: The fabulous little box is apparently an effect after several subsequent crashes of an application on OSX. There's an Apple help document about it, thanks for pointing that out in the comments, Michael.

Read more…

If your webservice breaks, at least give people a reason to smile when they read the error message -- like Technorati this morning:

Read more…

Uh, version 2.1.1 of the popular Wordpress blog software was compromised by a hacker who introduced malicious code into the version that was downloaded and installed by quite a few people across the globe.

While I wasn't directly affected (I hadn't upgraded to 2.1.1 yet), I upgraded another instance of WP on my server immediately because it did have the malicious code, as a quick grep for "ix" in the wp-includes directory showed.

When I decided to upgrade my own blogs to 2.1.2 as well today (skipping the bad release ;) ) I realized again how painful upgrading Wordpress is. While, once the code is in place, it's a one-click upgrade, getting the new code where it belongs is a pain in the arm. Code backup, database backup, disabling plugins, deleting code files (yet not deleting the user files that are heavily mixed up with actual application files), running the upgrade script, re-enabling the plugins.

Upgrading Wordpress should be easier than that. After all, it's an open source project. RERO is what makes it strong, and therefore even weekly updates should be desirable, but easy to do. So far, the Wordpress people haven't done much to solve this: And that is even more surprising considering how many releases they've pushed out since their 2.0 milestone.

I could imagine an options page in the admin interface automatically downloading a diff for the most recent version, trying to apply the patch (incl. merging) and failing gracefully if a conflict occurs (for extra credit, give advanced users an interface to resolve the conflicts). It should also do the DB backup and code backup itself: After all, it has at least read access to both its database and code directory.

This is a similar idea to what the Mozilla project calls AUS: The Application Update Service. It applies binary diffs to Firefox and friends in order to make staying up to date easier for people and save their precious time.

For now, I switched my wordpress instances to an SVN checkout of the latest tagged version, making the download process easier, but not solving the whole backup-disable-update-enable issue.

I like Wordpress -- and I don't seem to be alone: Wordpress is probably one of the most popular blog engines in the world. Now if they made updating as easy as installing it, they could show that their popularity has a good reason.

Read more…