I will go on a bit of a tangent about naming things because it's one of the three hard problems to solve in computing, the other being off-by-one errors (see what I did there?).
The term “Download ID” dates back to 2010 when it was only used to identify the user when they were downloading an update through Akeeba Live Update. It has never been a license key. The license of the software is GPLv3 and you can use the software itself without entering a Download ID. The Download ID is only used when you need to authenticate yourself to our server. It's more like an “Authentication Code” but naming it like that is even more confusing. Calling it a Download ID makes it easier for people to understand its primary purpose, giving you access to downloading updates.
When some third party services started using OAuth2 it made sense to use the same user identifier to control access to out authentication mediation service instead of creating a jarring and confusing user experience by either introducing yet another user identifier or changing the name of the Download ID. You have to also keep in mind that at any given time we may still have users on 5 to 8 year old software versions. Changing something in version X confuses people using earlier versions.
This brings me to the tangent. Remember that terms tend to have origins related to their original use, not their contemporary use. For example, the term “bug” in the context of computers has its origins to a literal bug (an electrocuted moth) stuck to a relay in a Harvard computer in 1947. Likewise you car's trunk doesn't hold a literal trunk and the hood is most definitely not a literal leather hood covering the engine compartment (which, by the way, no longer holds just the engine of the car, nor is it a compartment per se). By comparison, I believe that the origins of the term “Download ID” in our software are rather mundane and have definitely nothing to do with my native language. For what it's worth, I got my Certificate of Proficiency in English at the age of 16, I am almost 41 and married to an American. Between that, my work and the pandemic turning us all borderline hermits I seldom speak Greek anymore. You could pick me up and drop me in a city in the US and the only thing that I'd find truly alien would be turning right on a red light (outside North America you get flashing yellow arrows to explicitly allow that; you don't turn right on a red light).
Back to your question about Amazon S3. I definitely understand your reaction but it's overly pessimistic. You do not need to learn everything about Amazon Web Services to use S3. Amazon S3 is one of their most approachable services. Still, you have to figure out buckets and regions at the very least. It could be worse, e.g. the ungodly mess that's Azure.
An easier, cheaper alternative is BackBlaze B2. You may want to look it up.
Please, never retire or sell out.
I can't retire before 64 years old and I don't intend to sell out; I'd be so bored! You'll have to endure me for another 23 years and change at the very least :)
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!