61–70 of 95 posts
There are a lot of other options when it comes to locally hosted S3, minio has not been the best option for a long while.
It was used the most in introductory articles/examples maybe but there were better options
Earlier quoted context omitted.
> The S3 API is quite stable With so many things offering S3 compatibility, I’d say it’s de-facto standardized.
I can't see how Amazon is incentivized to avoid making any changes that break compatibility for their imitators, so long as their first party SDKs continue working. Standardized feels like it should be suffixed with "as long as Amazon doesn't ever feel like evolving the product further".
Also see Garage S3: https://garagehq.deuxfleurs.fr/
Moved to Garage, it's actually pretty easy to run and use. Would be even nicer if the official Docker image would support initializing a default bucket and access key from env variables instead of having to exec into the container and follow https://garagehq.deuxfleurs.fr/documentation/quick-start/ but that's not a dealbreaker. Note: I only needed the single-node install, it was either this or SeaweedFS. Also used Mi…
Um what? Opentofu was forked from the last MPL version of terraform, not a BUSL licensed version. This seems like an AI hallucination.
Earlier quoted context omitted.
The S3 API is quite stable and most new features are opt-in (e.g. ApplyIfModified) or auxiliary (e.g. S3Tables). It’s highly unlikely that S3 proper will break backwards compatibility for clients with any future API change. So if all you need is basic object storage that works with existing S3 clients, then MinIO is enough. The fork just needs to keep CVEs patched and maintain community hygiene (accept new PRs for sm…
> The S3 API is quite stable With so many things offering S3 compatibility, I’d say it’s de-facto standardized.
It's nice that people are taking this up, and one of the main benefits of open source in the first place. I have my doubts that this will succeed if it's just one guy, but maybe it takes on new life this way and I would never discourage people from trying to add value to this world. That said I increasingly have a very strong distaste of these AI generated articles. They are long and tedious to read and it really mak…
Indeed, the whole "Ironically, switching from Apache 2.0 to AGPL irrevocably makes the project forkable" section seems misguided. Apache 2.0-licensed software is just as forkable.
Earlier quoted context omitted.
I agree completely. I know everyone is tired of AI accusations but this article has all of the telltale signs of LLM writing over and over again. It’s not encouraging for the future of a project when the maintainer can’t even announce it without having AI do the work. It would be great if this turns into a high effort, carefully maintained fork. At the moment I’m highly skeptical of new forks from maintainers who are…
>I agree completely. I know everyone is tired of AI accusations but this article has all of the telltale signs of LLM writing over and over again. I mean, I'm more worried about the AI writing itself than people calling it out. The AI articles on HN are an absolute disease. Just write your own damn articles if you're asking the rest of us to read them.
• This is translated from my original Chinese post. I used Claude to polish the English — not a native speaker. Fair criticism on the LLM-ese; I'll tighten it.
• This fork exists because MinIO is a production dep in my PG distribution (Pigsty) and I needed working binaries + CVE patches. It's primarily for my own use; sharing it because others may have the same problem.
• We're deliberately conservative — no new features, just a drop-in replacement that behaves like the last OSS release with the console restored. Early commits will look thin.
> MinIO’s situation is actually more favorable — AGPL is more permissive for forks than BSL, with no legal gray area for community forks. Um what? Opentofu was forked from the last MPL version of terraform, not a BUSL licensed version. This seems like an AI hallucination.
> That’s the beauty of open-source licensing by design: a company can abandon a project, but it can’t take the code with it.
This is a FREE license, which is not just open source. It's open source + more.