BTW Pete, Aeva Media was already (since last April) modified to remove the auto-update code.
And yeah, having all plugins check for new versions will definitely be a nightmare (if only because sm.org itself doesn't do it -- only a few mods do that, and look at where they're at now.)
That's one of the reasons why I suggested requesting that all plugin authors host their 'main' download somewhere else, including the URL to request new version updates.
Maybe we could do it systematically. For instance instead of offering to upload the mod file (which we could still have as a fallback), we'd put priority on asking authors to provide: (1) a direct link to the mod (version number free, so that they don't have to update the URL every time), (2) provide inside their plugin definition file a direct link to the version number request file (we could have some kind of a standard file for this which they'd simply need to fill in and then upload somewhere).
I appreciate the update Nao. I think it was the honorable thing to do.
Well it's something I'd wanted to do for a long time but I postponed it because I didn't think the load would be that taxing on the server... I mean there are at most 10 to 15k installs of Aeva Lite/Media around, each doing at most one request to one HTML page every day (if they didn't disable the lookup code), so that's one request every ten seconds. At most.
Hmm okay it's still a lot more than zero...
:PI mean I was expecting that if it was a load on the server, I should have received a request about it when I was active on Aeva -- i.e. over a year ago.
I'll install it. I've scheduled some time for that tomorrow (I always like to do some testing before even a very simple install like this).
My little forum is not going to make a big difference to the hammering AEVA installs are giving the site, but I'll do my little part.
At the very least, with the user agent being disabled, it'll only be 'ghost' requests.
The AEVA mod was completely invisible for only a short while -- only until the folks at Simple Machines and the SMF customization team found a less-restrictive way (blocking your unique user agent) to give the customization site some relief from AEVA's barrage of requests. I am told that it would be difficult to re-enable auto-update access now. The AEVA traffic level is that heavy.
It depends on whether the traffic gets manageable. Then they can re-enable the auto-update for a few days, and it should be enough to get all installed Aeva's to update their version number and ask admins to update to the latest version.
As you can see, I added the infamous support for 'youtu.be' URLs as an incentive for noobs to upgrade one final time.
