

It's not working.. Is there any settings I can modify to turn this off?DaveG wrote: ↑Sat Oct 13, 2018 4:04 am
- Download the last Flagfox 5.2.x ESR version from the official page: https://flagfox.wordpress.com/download#5.2
- Override the requirement for only Mozilla signed addons (as they no longer allow these versions posted to AMO) by following the instructions on that download page. (Firefox 52 ESR required)
- Install your dowloaded installer file (XPI) via the Firefox Addon Manager: Go to Firefox menu -> Add-ons -> Gear menu (next to search field) -> "Install addon from file..." (autoupdates are no longer supported for old addons, but if you upgrade to Firefox 57 or 60+, it can be updated to current versions)
Same here. comes and goes. I checked the storage.js file and also haveavada wrote: ↑Sun Feb 11, 2018 10:06 am
It seems more like it appears erroneously, then disappears on its own. I checked the config file and it has "{"warn.tld":"disabled","warn.stale":"disabled"}" in it. Maybe I could work around it via CSS if I could get a selector to the Flagfox specific notification.
(I forgot to mention, but I'm on Waterfrox 56.0.3)
Code: Select all
{"warn.tld":"disabled","warn.stale":"disabled"}
BTW, did you just change the if (ipdb.daysOld > 90) statement to something else like if (ipdb.daysOld = 0)?
Just "if (false)" should be more than fine. The use of a single equals is assignment in JS; double or triple is needed for comparison.click-click wrote: ↑Tue Mar 26, 2019 12:40 pmBTW, did you just change the if (ipdb.daysOld > 90) statement to something else like if (ipdb.daysOld = 0)?
If you already have Flagfox 5.2.11 (last ESR version), then yeah, you should be able to just dump in the newer files and everything other than Geotool will work. I backported the minor changes to the IPDB manifest format in 5.2.7. Geotool will reject you when it sees an invalid HMAC, but Geotool should already be rejecting such an old Flagfox version anyway. If you want to use Geotool, either use the current version of Flagfox or simply use Geotool by itself, not automatically called from Flagfox (CAPTCHAs may apply to throttle traffic; all of this is necessary to prevent abuse from killing the server, yet again).click-click wrote: ↑Tue Mar 26, 2019 12:15 pm@DaveG
Is there any way to just replace the Flagfox DB with a newer one?
Rejoice! I've found the fix:click-click wrote: ↑Tue Mar 26, 2019 12:15 pmSame here. comes and goes. I checked the storage.js file and also haveavada wrote: ↑Sun Feb 11, 2018 10:06 am
It seems more like it appears erroneously, then disappears on its own. I checked the config file and it has "{"warn.tld":"disabled","warn.stale":"disabled"}" in it. Maybe I could work around it via CSS if I could get a selector to the Flagfox specific notification.
(I forgot to mention, but I'm on Waterfrox 56.0.3)Code: Select all
{"warn.tld":"disabled","warn.stale":"disabled"}
Right now Flagfox is quiet. When the pop-ups return, I'll check the storage.js to see if something changed. The last resort will be
to edit the addon package previously mentioned in this thread.
@DaveG
Is there any way to just replace the Flagfox DB with a newer one?
Hi Dave, thanks for creating and providing support for Flagfox since long time ago. We old timers still can't move on to the new browser because we still need the old addons. unMHT, Flashgot, and DownThemAll are some of essential addons I need for browsing. I bet those will never be ported because of how WebExtension works.DaveG wrote: ↑Mon Apr 22, 2019 1:06 amBottom line: We're talking about an old version of an addon that I should have completely ended support for in 2017, provided an extra year of extended support updates to, and is now end-of-life 2 years later. The codebase it depends on has been, itself, end-of-life since last year as well. This has to end at some point, which is one way or another long past due.
How about you make a "final" legacy version of Flagfox which disable the notification?DaveG wrote: ↑Mon Apr 22, 2019 1:06 amNote that I'm only telling you what is technically possible here, for you own personal hackery. Uploading a modified version of Flagfox to be hosted for others is a violation of the Flagfox license. (not that it can even be run in any current version of Firefox, anyway, as Mozilla got rid of the ability to disable addon signing verification) There's already enough garbage scraper sites out there hosting official versions on dubious pages that show up in Google searches for Flagfox, and I'd really appreciate it if people didn't add to the mess with unofficial versions. Whatever you do on your own computer is your own decision, though, again, I'd prefer you accept that trying to keep things on life-support here is not a good idea.
As I only use Flagfox to view the flag and location, I'm not affected by using the old version. The IPv4 locations have not been changed for years anyway.DaveG wrote: ↑Mon Apr 22, 2019 1:06 amIf you already have Flagfox 5.2.11 (last ESR version), then yeah, you should be able to just dump in the newer files and everything other than Geotool will work. I backported the minor changes to the IPDB manifest format in 5.2.7. Geotool will reject you when it sees an invalid HMAC, but Geotool should already be rejecting such an old Flagfox version anyway. If you want to use Geotool, either use the current version of Flagfox or simply use Geotool by itself, not automatically called from Flagfox (CAPTCHAs may apply to throttle traffic; all of this is necessary to prevent abuse from killing the server, yet again).