Attribution needs to be explicit for Open Source Licenses prominently available for customers to look at.

Making money off from another product calling it your own innovation is plagiarism.

https://www.weka.io/blog/cloud-storage/amazon-s3-protocol/

There is never a mention of that it uses MinIO underneath.

But it explicitly shows that it's using Minio when the application is actually used?

Sure, it's totally uncool to not mention Minio on their site and that's a massive shame but, as far as I'm aware, nothing in the license would require Weka to explicitly mention they're using Minio in their advertising/marketing like the provided link?

Nutanix does not carry EULA or reference even today while continuing to use it.

Read Apache v2 attribution clauses.

> while continuing to use it.

But the parent to your comment says they don't use it (any more)???

Of course they use it, its there in their container :-)

Ask your corporate to pay for it.

I am glad they kept AGPLv3 to keep freeloaders in corporate under check.

No, gateway mode is EOL'ed and it is not taking any new features

Oh I see. I checked the repository and it's being stopped very soon: https://github.com/minio/minio/issues/14331

AWS drive speed has not changed much, neither is their network for the same instance and model.

https://github.com/minio/minio/tree/master/docs/distributed#... - MinIO has been strictly consistent from Day 1.

AWS S3 recently launched strict consistency.

Wasabi is eventually consistent for overwrites ``eventual consistency for overwrite HTTP PUTs and HTTP DELETEs``

This is not the same.

Yes, I'm aware.

https://github.com/minio/minio is here

For all enthusiastic folks you may want to read more here on SipHash comparisons

https://github.com/fwessels/HashCompare/blob/master/README.m...

https://github.com/fwessels/HashCompare/issues/1

There is no C++ in the code, it is a native Go library of Google's HighwayHash implementation