Everything is on fire, but at least it’s not my fault

Mozilla screwed up and failed to renew the code signing certificate used for addons, resulting in mass-disabling virtually all addons for everyone. Yay. Even lightweight themes are affected, somehow, and they’re just glorified PNGs. Exactly one of the addons I have installed survived the armagadd-on, which is literally what Mozilla is naming it internally. Flagfox is in the very long list of the affected. Someone from Mozilla even linked to one of their forums on Twitter and Mozilla’s server was overloaded, so yeah… they’ve got some problems at the moment.

The only thing I can think of to attempt to work around things on my end would be to rush out an update just to resign, in the hopes that they have a new cert online and it’s just old versions that have expired. However, I don’t actually know if that’d help, and due to the sheer scale of the breakage here, I think it’s best I touch nothing for the moment. Everyone’s affected, so Mozilla is going to have to come up with a fix for everyone, one way or another, hopefully ASAP.

Update 1:
Mozilla released Firefox 66.0.4 and 60.6.2 (ESR) updates which should fix the majority of this issue. Please update.
(update instructions; more info from Mozilla)

Update 2:
Mozilla released another pair of updates, now Firefox 66.0.5 and 60.6.3 (ESR), which should fix things more reliably. Apparently some antivirus programs could break things (as they often do) and very old master passwords could cause issues. In any case, it’s fixed again, for realzies this time.

Advertisement

The AMO beta channel has been removed

For anyone who (actually) reads what I post here, just a quick note: Mozilla removed the beta channel from Mozilla Add-ons. (The actual timing was delayed from the date of their post. I’m not sure exactly when the change actually went live.) This means that for all addons which used this feature, they no longer have a simple method to have users test addon pre-releases via AMO. Flagfox 6.0 was my most recent use of this system, and it was invaluable. All users who had installed any beta channel version should automatically be updated to the latest stable channel version. Just to be clear, this applies to every addon Mozilla hosts on AMO, not just Flagfox.

I may do another Flagfox alpha/beta in the future, as I have done multiple times in the past, but it’ll require more time and effort, and will have a little less visibility. If/when I do so, this irregularly used blog is where I’ll announce it.

On an unrelated note: The Flagfox 6.0.x and 5.2.x monthly updates are pending, and as usual will be available at the end of the month. I’ve been considering switching from an end-of-month schedule back to a mid-month schedule, but I’ve simply not actually done so yet. Maybe probably next month.

Posting status info to AMO is a pain

The Flagfox 6.0 update to support Firefox 57 (prior post here) is still slowly being worked on, though it’s going much slower now due to bad luck and timing, as I’ve gotten rather sick. It’s not that serious; I’m not dying, or anything, but I’m coughing horribly, sleeping badly, and am a bit lightheaded in addition to just feeling like crap. (The person I caught this from is still sick, as well, so I don’t know when this will be out of my system.) This is not conducive to programming well, let alone quickly, in an alien API, often having to deal with some really stupid junk that I’ll be reporting to Mozilla via bug reports after all this is done. Again, just to reiterate, I am the only Flagfox developer and this is a hobby project.

Anyway, it’s time for me to post another explanation of a problem caused by a recent stupid Mozilla decision:

If you’re wondering why I hadn’t put up any Firefox 57 support status update message on Flagfox’s page on the Mozilla Add-ons site until today, it’s because doing so is shockingly difficult, especially as of Mozilla’s latest revision of the website. (it’s crap in a variety of ways, but this one is particularly annoying) Previously, there was a “Developer’s Comments” section in addition to the “Add-on Description” section (currently labeled “About this extension”) where I could put updates like this, though at some point they started hiding it by default, which was annoying. Now it’s gone completely. I still seem to have it available to configure in my settings, but it doesn’t actually show on the page, even with all the stupid dead-space below the mostly hidden by default description (again, there’s a lot of dumb in their recent site refresh). My guess is some Mozilla web developer thought it was pointlessly redundant, however it’s most definitely not. Updating the addon description requires editing each and every one of the dozens of Flagfox description translations into many of the various languages supported by Flagfox. Updating the developer’s comments, on the other hand, was simple; there was only English, shown to everyone (if you can’t read it, that’s a problem, but at least it’s there and you can see it, and maybe attempt automatic translation, potentially using Google Translate via the built in Flagfox action…). There is no mass-edit/change/upload feature for Mozilla Add-on’s listing data, though it has of course been requested by many addon developers over many years. (unless there’s some secret way to do it they’ve added at some point and not told anyone about) As a result, the simple logistics of me putting a message on that site that can actually be read by more than a quarter or so of the Flagfox userbase required me to slowly go through the menu of listed translations and delete each description (there isn’t even a delete button; I have to click “edit”, then select all, then hit delete, then save), one by one, until just the English one remains for me to edit and show to all. This is stupid, but sadly, the least stupid thing I’ve had to deal with during this transition to Firefox 57.

Flagfox 5.0 update Q & A

I’ve been getting quite a few emails and bits of feedback from various sources, so I thought I may as well put up a post centralizing some common questions and answers.

Can I make the flags smaller?

Yes, however some of the more detailed flags don’t look quite right when you do. See here for more info. It’s just a pref to set via about:config.

Why didn’t you add the size setting to the options?

I didn’t want to include an in-GUI option that didn’t work perfectly. Detailed flags just don’t look right at smaller sizes. Those who reply back to me after I point them to how to change the size often respond “oh, yeah, I see that now”. Having it just in about:config lets me easily leave it as a raw number you can play with, as well.

Will you add back the old flag icons?

No. The old sets are not maintained anymore and full of out-of-date flags. Even attempting to properly figure out how many need fixing would take forever and I don’t have the capability to make replacements that match the styles. They were also bad for various other reasons, hard to make out for many people, and the alternate set was actually upscaled to fit into the still tiny space. It’s quite frankly strange that there are a few people who rudely demand that I revert something I worked on for months because they’re used to the old style. (I still get one guy creating throwaway accounts on Mozilla Add-ons to abuse the review system to repeatedly rant about the lack of status bar support many years after the fact; don’t get me started on the angry email about not supporting a version of Firefox that runs on Windows 98 anymore…) Yeah, it’s a UI change, and there’s a bit of subjectivity, but just because you don’t like it as much as everyone else doesn’t mean you should be an asshole about it.

Why didn’t you add the ability to pick between 3 different sets?

That would be a complicated mess and bloat the installer and update sizes. Again, there’s lots of holes in the old sets that I would have to attempt to (poorly) maintain.

Can’t you just add an option to the options dialog for me?

No. Even if I want to add an option, it needs to be translated into around 40 languages. Flagfox has around a million users and most of them don’t use it in English. The translators are all volunteers and getting any localization updates takes a month or two. Yep, there are downsizes to localization. (though, the positives outweigh the negatives)

How can you say the old sets were out of date? They even had the new Libyan flag.

Yeah, because I added it. There hasn’t been an update to either set in about 6 years, and the primary one was more out of date than the alternate one. I have personally been making an attempt to hack in updates over the years. They didn’t match at all. The size of the old sets was too small to work with without heavy stylization, and I’m no image editor pro. I was forced to limit which flags I could update to avoid making them a complete and total mess. Minor updates had to be ignored. Each individual update was a pain in the ass to do, taking a lot of time, and done always late as I didn’t exactly have a way to know when any of the 250 flags needed changing. It was an unmaintainable mess and the primary reason I decided I had to work towards a better solution. This new set is maintainable. I can actually detect and release updated versions rapidly. If you haven’t noticed, there have been a few more changes in the world as of late, and this is what I need to do to keep up.

There is no Flagfox development team. It’s just me; one guy sitting on a couch with an old laptop. It’s not a full-time job unless you decide to donate quite a lot to keep things going. There is one person working on Geotool. It seems there are quite a few people who can’t grasp that software is written by living people, not always a giant corporation or other organization. This is a free service and this new flag set is the only practical way forward that makes giant improvements in accuracy, usability, and appearance.

Can I have a monochrome mode?

Not trying to be rude, but this question made me laugh. I don’t even want to attempt to count how many countries have tri-color flags. If I made a way for the flags to be monochrome to match other buttons in your theme, you wouldn’t be able to tell many of them apart. People had enough trouble trying to tell apart Ireland and Italy in the old sets. No, monochrome will not work here. 😉

Why are the flags different sizes?

Flags are actually different sizes. Different flags have different aspect ratios. You may be used to flag image stylizations where they’re all squished and changed to be the same size. That is not real life. The 250+ nations of the world have not all gotten together to standardize their flag aspect ratios.

Why don’t the flag colors match?

Flags are actually different colors. The red of Canada’s flag is not the same red as America’s flag. Again, no, the world has not color coordinated their flags. I decided that if I was going to make a new flag set I would do it correctly and respect the actual color choices of each country. Plus, it’s much easier this way.

I don’t like flags at all. Can I have a text only mode?

I’ve been considering this a while as an accessibility feature. It was requested specifically recently by a user, so yes, I’m going to look into implementing this feature at some point.

Why did I put the first-run page on my blog?

If I were to put all 10 translations and all the needed styling to get it working inside the installer it would really bloat up the download size for the update for everyone. Putting it up here also lets me put in updates to links if need be.

Why only PayPal?

Mozilla Add-ons only allows PayPal. Yes, this sucks. I have also provided a second route to donate via Amazon which a few people have opted to use. At request I also put up a Bitcoin address, though as of yet nobody has used it. I would have preferred to also have up a Litecoin address, but could not do so due to technical issues with the client. If anyone has an issue with PayPal, please read this. You can email me to get the email address you need to use to send a donation with PayPal directly if Mozilla’s system does not work for you.

Why haven’t you responded to my email/review/post/comment?

I’ve responded to most people as quickly as I can. I’m ignoring the ones cursing at me. I’m noticing that some of the less coherent ones are getting caught in the spam filter, and I’m inclined to not dig through hundreds of spam emails to find them all.

How has the feedback been thus far, in general?

Overwhelmingly positive. Counting all routes, including contributions, I’ve gotten hundreds of thanks and a couple dozen or so complaints.

Note that the contribution system allows for posting a message, however near as I can tell, there’s no way for me to actually view that. Mozilla doesn’t seem to forward that correctly or put it up anywhere else I can find. Sorry, I have no control over that.