Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

MinIO is now in maintenance-mode

github.com

Post reply on HN
Print view View original

301–310 of 338 posts

Re: MinIO is now in maintenance-mode

#301

Post by lukaslalinsky »

tetha wrote: post #235
ahepp wrote: post #182

Earlier quoted context omitted.

Wait, what's the consensus on this? Are they saying that using object storage over a standard network API which they didn't even create, makes your application a derivative work of the object store? Or just that the users would need to make minio sources, including modifications, freely available? I guess that's kind of the big question inherent to the AGPL?

From my understanding, you would not be allowed to sell an "S3 compatible storage" as a service based off of Minio or another AGPL licensed S3-compatible storage solution, especially if you modify the source code of minio in any way and then serve that to your customers. If you use Minio or another AGPL licensed service internally to support your own product without a customer ever touching it's API, it should be fin…

What in AGPL prevents this? AGPL only forces you to open source your modified version of MinIO/whatever. GPL forces you to open source only if you actually distribute the modified version, which gets muddy in the context of network services, therefore AGPL was created. If you want to build a commercial service based on AGPL software, there is nothing stopping you doing that.

Re: MinIO is now in maintenance-mode

#302

Post by reedciccio »

creatonez wrote: post #288
spicymaki wrote: post #219

Stallman was right. When will the developer community learn not to contribute to these projects with awful CLAs. The rug has been pulled.

Except... the FSF is actually on the extreme opposite end of this issue. They do formal copyright assignment from the GNU contributors to the FSF. This way, they have a centralized final say on enforcement that is resistant to copyleft trolls, but it ultimately allows the theoretical possibility of a rugpull.

The FSF can't pull the rug because of its bylaws

Re: MinIO is now in maintenance-mode

#303

Post by lukaslalinsky »

createaccount99 wrote: post #295
phoronixrly wrote: post #122

Earlier quoted context omitted.

It is also useful to remember that MinIO has historically held to an absurd interpretation of the AGPL -- that it spreads (again, according to them) to software that communicates with MinIO via the REST API/CLI. I assume forks, and software that uses them will be held to the same requirements.

I thought that literally was the point of AGPL. If not, what's the difference between it and GPL3?

AGPL changes what it means to "distribute" the software. With GPL, sending copies of the software to users is distribution. With AGPL, if the users can access it over network, it's distribution. The implication is that if you run a custom version of MinIO, you need to open source it.

Re: MinIO is now in maintenance-mode

#304

Post by Zambyte »

import wrote: post #28
Dachande663 wrote: post #19

Does anyone have any recommendations for a simple S3-wrapper to a standard dir? I've got a few apps/services that can send data to S3 (or S3 compatible services) that I want to point to a local server I have, but they don't support SFTP or any of the more "primitive" solutions. I did use a python local-s3 thing, but it was... not good.

rclone serve s3, could be.

I just learned about the rclone serve subcommand the other day. Rclone is not exactly niche, but it feels like such an underrated piece of software.

Re: MinIO is now in maintenance-mode

#305

Post by boomskats »

victormy wrote: post #233

Big thanks to MinIO, RustFS, and Garage for their contributions. That said, MinIO closing the door on open source so abruptly definitely spooked the community. But honestly, fair play to them—open source projects eventually need a path to monetization. I’ve evaluated both RustFS and Garage, and here’s the breakdown: Release Cadence: Garage feels a bit slower, while RustFS is shipping updates almost weekly. Licensing:…

RustFS vs MinIO latest performance comparisons here: https://github.com/rustfs/rustfs/issues/73#issuecomment-3385...

Re: MinIO is now in maintenance-mode

#306

Post by jerf »

zokier wrote: post #185
jerf wrote: post #152

Earlier quoted context omitted.

That may be what S3 is like , but what the S3 API is is this: https://pkg.go.dev/github.com/aws/aws-sdk-go-v2/service/s3 My browser prints that out to 413 pages with a naive print preview. You can squeeze it to 350 pretty reasonably with a bit of scaling before it starts getting to awfully small type on the page. Yes, there's a simple API with simple capabilities struggling to get out there, but pointing that out is…

> That may be what S3 is like, but what the S3 API is is this: https://pkg.go.dev/github.com/aws/aws-sdk-go-v2/service/s3 > My browser prints that out to 413 pages with a naive print preview. You can squeeze it to 350 pretty reasonably with a bit of scaling before it starts getting to awfully small type on the page. idk why you link to Go SDK docs when you can link to the actual API reference documentation: https://d…

Because it had the best "on one HTML page" representation I found in the couple of languages I looked at.

Re: MinIO is now in maintenance-mode

#307

Post by lionkor »

gethly wrote: post #132

There is https://github.com/seaweedfs/seaweedfs I haver not used it but will be likely a good minio alternative for people who want to run a server and don't use minio just as s3 client.

Sadly there's nothing in the license of seaweedFS that would stop the maintainer from pulling a minio -- and this time without breaking the (at least spirit of the) terms of the project's license.

Not an issue at all until they do.

Re: MinIO is now in maintenance-mode

#308

Post by raxxorraxor »

victormy wrote: post #233

Big thanks to MinIO, RustFS, and Garage for their contributions. That said, MinIO closing the door on open source so abruptly definitely spooked the community. But honestly, fair play to them—open source projects eventually need a path to monetization. I’ve evaluated both RustFS and Garage, and here’s the breakdown: Release Cadence: Garage feels a bit slower, while RustFS is shipping updates almost weekly. Licensing:…

> open source projects eventually need a path to monetization.

I don't think open source projects need a path to monetization in all cases, most don't have that. But if you make such a project your main income, you certainly need money.

If you then restrict the license, you are just developing commercial software, it then has little to do with open source. Developing commercial software is completely fine, but it simply isn't open source.

There is also real open source software with a steady income and they are different than projects that change to commercial software and we should discriminate terms here.

Re: MinIO is now in maintenance-mode

#309

Post by chrislusf »

written-beyond wrote: post #292
chrislusf wrote: post #249

Earlier quoted context omitted.

This is Chris and I am the creator of SeaweedFS. I am starting to work full time on SeaweedFS now. Just create issues on SeaweedFS if any. Recently SeaweedFS is moving fast and added a lot more features, such as: * Server Side Encryption: SSE-S3, SSE-KMS, SSE-C * Object Versioning * Object Lock & Retention * IAM integration * a lot of integration tests Also, SeaweedFS performance is the best in almost all categories…

Congratulations on earning that opportunity! Thank you for your work. I was in a position where I had to choose between minio and seaweed FS and though seaweed FS was better in every way the lack of an includes dashboard or UI accessibility was a huge factor for me back then. I don't expect or even want you to make any roadmap changes but just wanted to let you know of a possible pain point.

Thank! There is an admin UI already. AI coding makes this fairly easy.

Re: MinIO is now in maintenance-mode

#310

Post by valyala »

cortesoft wrote: post #212
valyala wrote: post #207

What is the purpose of MinIO, Seaweedfs and similar object storage systems? They lack durability guarantees provided by S3 and GCS. They lack "infinite" storage promise contrary to S3 and GCS. They lack "infinite" bandwidth unlike S3 and GCS. They are more expensive than other storage options, unlike S3 and GCS.

We use it because we are already running our own k8s clusters in our datacenters, and we have large storage requirements for tools that have native S3 integration, and running our own minio clusters in the same datacenter as the tools that generate and consume that data is a lot faster and cheaper than using S3. For example, we were running a 20 node k8s cluster for our Cortex (distributed Prometheus) install, monito…

Consider migrating to VictoriaMetrics and saving on storage costs and operations costs. You also won't need MinIO, since it stores data to local filesystem (aka to regular persistent volumes). See real-world reports from happy users who saved costs on a large-scale Prometheus-compatible monitoring - https://docs.victoriametrics.com/victoriametrics/casestudies...
Post reply on HN