operations-mediawiki-config VS minio

> Configuration is just a short artifact. It's not a creative work and is therefore not copyrightable at all, whether by AGPL or otherwise.

I'm doubtful. For example https://github.com/wikimedia/operations-mediawiki-config is wikipedia's config. It is not short, and much of it is complex enough i think it would be copyrightable (ianal)

I agree though a very traditional list of key value pairs that are simple facts like where to find the db, might lack creativity to be copyrighted (ianal). But how many real deployed systems have that simple a config. More generally i would prefer that the license was less ambigious about this especially in an international context (e.g. rules are totally different in uk over what can be copyrighted)

> I'm not convinced obscurity helps against spam at all. DKIM and blocklists have done much more against email spam than any form of "security by obscurity" corporate scheme has.

Gmail et al use techniques beyond dkim that are secret. However i meant more like web spam where you can't just rely on source vouching for users. For example on wikipedia there is a feature where admins can write "code" that block patterns in edits. When used against persistent vandals, they are often secret lest they use the info to adjust behaviour. That's the type of thing i mean.

> if you are coordinating with the developers, then you have their explicit permission to temporarily withhold those changes (AGPL copyright holders can still grant exceptions to the license)

That only works if one entity holds all the copyright. Even then, does that mean forks cannot have coordinated disclosure?

You could refer to big OSS project Makefiles to take a look, what could be there, for example: https://github.com/minio/minio/blob/master/Makefile

Backblaze's B2 is compatible with AWS S3 that also implemented in selfhosted minio

https://github.com/minio/minio is what comes to my mind

For example minio is written in go and quite nice.

> Iteration speed and blazing fast automated tests.

Wholeheartedly agreed!

It is also nice to have that additional assurance of being able to self-host things (if ever necessary) and not being locked into a singular implementation. For example, that's why managed database offerings generally aren't that risky to use, given that they're built on already established projects (e.g. compatible with MySQL/MariaDB/PostgreSQL).

> When I discovered minio, I suddenly got much more confident coding against s3.

MinIO is pretty good, but licensing wise could become problematic if you don't work on something open source but ever want to run it in prod. Not really what this discussion is about, but AGPL is worth mentioning: https://github.com/minio/minio/blob/master/LICENSE

That said, thankfully S3 is so common that we have alternatives even to MinIO available, like Zenko https://www.zenko.io/ and Garage https://garagehq.deuxfleurs.fr/ both of which are good for both local development as well as hosting in whatever environments necessary.

https://github.com/minio/minio/discussions/13571#discussionc...

https://github.com/minio/minio/issues/13308#issuecomment-929...

Lets just say they have a weird take on what constitutes agpl-compliant

Didn't know that MinIO used to be Apache licensed. This [0] is the commit that changed it.

Since the S3 API largely remained the same over the last two years, it might be an option to use the Apache version, if AGPL is not possible. Of course, that would lack security fixes that were done in the meantime.

There is also a discussion [1] about that license change.

[0]: https://github.com/minio/minio/commit/069432566fcfac1f105367...

[1]: https://github.com/minio/minio/issues/12143

It seems they might be psychos, they are misrepresenting what AGPL allows all over their issue tracker, for example this: https://github.com/minio/minio/issues/12829#issuecomment-889...

> Also NOTE: I need to remind you are under AGPLv3 violation here if you are using MinIO with proprietary purposes. Please consult a software lawyer for more information.

MinIO had a large investment round at unicorn valuation at the end of last year. Watch them desparately move up market (or more like flailing around) to recoup that investment.

Meanwhile they cannot get their software to work on ext4 and it is apparently ext4s fault[0].

[0] https://github.com/minio/minio/issues/16602#issuecomment-142...