Flagfox 6.1.18 for Firefox 60+ has been released and will be available for update and download from AMO as soon as it is approved by Mozilla.
Flagfox 6.1.18 changelog:
- IPv4 & IPv6 address location database updates for September 2019
I had planed to update the API used to run user-JS in custom actions to use a newly created one, but I didn’t yet. It is delayed until whenever it is that I actually finish that. For now, this is just the routine monthly IPDB update.
Flagfox 6.1.17 for Firefox 60+ has been released and is available for update and download from AMO.
Flagfox 6.1.17 changelog:
- IPv4 & IPv6 address location database updates for August 2019
Flagfox 6.1.16 for Firefox 60+ has been released and is available for update and download from AMO.
Flagfox 6.1.16 changelog:
- IPv4 & IPv6 address location database updates for July 2019
- Updated country names list for North Macedonia name change (en/de/ru)
The only locales Maxmind updated for Macedonia, now North Macedonia, were English, German, and Russian, so those are the only 3 locales that have this one string properly translated. Everyone else gets a fallback to English for it. Eventually I need to find some way of getting translators access to update things in here again. Babelzilla is still stuck in the stone-ages and doesn’t support WebExt packaged addons (last I checked), though I’ve yet to test an inglorious hack on my side of things that might get things working with shims (assuming anyone would still use Babelzilla). For now, though, this is “fine”.
Oh, and whilst I did notice the change when first announced, I totally forgot about it until I was recently reminded by watching Jeopardy (a long running US TV quiz show), which had Macedonia’s name change as a final question. My mind went: “I know this… read that somewhere… somebody in Europe that starts with an ‘M’… oh… yeah… I never did get around to updating Flagfox for ‘North Macedonia’, did I?…” So, yeah, thanks Jeopardy!
Mozilla Add-ons is having some sort of issue and has still not approved the file for release. I’ve yet to receive an explanation, one week later. I will update here once this update is actually released.
I’ve still yet to get a reply from AMO as to what went wrong, but this version has finally been approved.
Flagfox 6.1.15 for Firefox 60+ has been released and is available for update and download from AMO.
Flagfox 6.1.15 changelog:
- IPv4 & IPv6 address location database updates for June 2019
As far as I’m aware, Mozilla has completely fixed the catastrophic addon authentication breakage from last month, so everything should be working fine again.
On a separate note, Mozilla seems to have finally gotten around to fixing some issues with their addon submission validation system and it is no longer convinced the locale files are full of naughty words.
Flagfox 6.1.14 for Firefox 60+ has been released and is available for update and download from AMO.
Flagfox 6.1.14 changelog:
- IPv4 & IPv6 address location database updates for May 2019
Due to Mozilla’s recent catastrophic screw up with all addon signing certificates, you should make sure to upgrade to the latest version of Firefox: 66.0.5 for main release and 60.6.3 for ESR release. (formerly 66.0.4 & 60.6.2, prior to second fix update) Virtually all addons for all people on the planet are effected, Flagfox included. (a small handful continued working, but it’s rare; yes, this was as bad as it sounds) Older versions of Firefox can work if you let it install the earlier partial fix via the studies system, though many people disable that. (update instructions; more info from Mozilla)
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.
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)
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.