SoylentNews is people
SoylentNews
Mozilla plans to remove all legacy add-ons from their portal.
Support for Firefox ESR 52 will end on September 5, in two weeks, meaning there won't be any official Firefox version that supports legacy add-ons anymore.
Mozilla said today that following this date, it plans to start the process of disabling legacy add-on versions on its add-ons portal located at addons.mozilla.org (also known as the AMO).
"On September 6, 2018, submissions for new legacy add-on versions will be disabled," said Caitlin Neiman, Add-ons Community Manager at Mozilla.
"All legacy add-on versions will be disabled in early October, 2018. Once this happens, users will no longer be able to find [extensions] on AMO," she added.
Isn't modern FOSS great?/s
I can run old Blender if I need. Or go over all the archived .deb from past Debian releases. But Mozilla seems to be special. Time to call the Archive Team or the Wayback Machine.
(Score: 2) by MichaelDavidCrawford on Thursday August 23 2018, @12:47AM (1 child)
I expect you can figure out why.
I even did that for Windows so quite likely I possess a complete set of WinXP updates starting with its final service pack.
I took a stab at doing that for Win8.1 then quickly conceded it was just not possible for just one person to do so.
Were I to continue using windows for anything other than to do a fresh install in a VM EVERY SINGLE TIME I NEED WINDOWS FOLLOWED BY MY DELETION OF THE VM I'd set up a local Windows update server.
Yes I Have No Bananas. [gofundme.com]
(Score: 4, Informative) by jmorris on Thursday August 23 2018, @01:36AM
You are doing the VM thing wrong. You don't reinstall and patch up Windows from scratch every time!
Install. Update. Take a copy of that image for safe keeping. Now use whatever your virtualization calls it to flip writes into a different file/stream/snapshot that you can discard. Install whatever you want to use, use it, then roll back to the perfect blank install. Rinse, repeat as needed. Never again worry about crap left in the registry when you uninstall, never worry about getting infected, never even worry about downloading a Trojan horse version of something since no matter what it won't live beyond the rollback unless it is so utterly vile that it breaks out of virtualization and attacks the real OS underneath. Avoid the temptation to add a persistent volume because if things CAN live squirreled away on D:, eventually something will. Make an scp client part of the base install and move the couple of files you need to keep out manually before wiping the image back to base.
Once in awhile switch off the rollback, do a fresh round of updates to the base image, take a fresh "just in case" backup of the image file and switch the rollback on again.