I am not going to be removing either access method. I know for a fact that a lot of third party S3-compatible services will only work with path-style access for the reasons I explained and your host all but confirmed. So no worries there.
BTW, would you consider adding "PlanetHoster N0C Storage" to your dropdown of pre-configured cloud hosting for post-processing?
No. I do not add any third party S3-compatible services as its own post-processing engine.
It's not just adding a dropdown value. It's creating its own post-processing class, configuration file, and language files. This is a lot of busywork and it becomes a proper nightmare when I need to refactor anything as I now no longer have one S3 post-processing class to refactor, I have multiple. The more of these there are, the more likely it is I will make a mistake unless I can explicitly test with it.
This means I will need to buy access to every supported service, regardless of how many people use it. Since the vast majority of S3-compatible services don't have a free tier and are only offered tied to some other expensive service I will have to be spending a lot of money just to maintain the code.
Since I would be directly supporting a service, I am not responsible for any changes in that service even though I don't get paid from the service provider, nor am I consulted before any changes take place. I have to do a lot more work keeping up with many more services and go through the headache of communicating with my clients even when the communication from the service itself is as clear as mud. This adds a lot of work and responsibility which costs money and can lose me clients, without bringing in any income.
This is even worse considering the fact that if I add any single one random service I have to add any other random service nobody has heard of, even if it's used by one person and they ask me to. There are hundreds of them out there. It's trivial for any half-competent host to install and configure OpenStack and its S3-compatible API. Having to support all these hundreds of random installations —or each one of my clients' bespoke ownCloud S3-compatible installation— in Akeeba Backup becomes a VERY expensive proposition, to the point that I need to triple or quadruple the price of my software. This, in itself, will lose me clients.
Finally, once I start adding specific S3-compatible services people mistakenly understand that if it's not listed it's not supported. This loses me both potential and current clients.
To sum it up, I get a lot more work to do, I have to spend a lot more money, and I get to lose clients as a result. Or I can do no work, don't spend any money, and not lose clients. I think it's very clear which is the only reasonable course of action here. I am not lazy, I did my risk analysis before saying “yes” to everything :)
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!
