iroh VS garage

If you're talking about this https://github.com/n0-computer/iroh ... Iroh is a p2p file syncing protocol. That's not even close to the same wheelhouse as SeaweedFS?

Totally biased founder here, but I work on https://github.com/n0-computer/iroh, a thing that started off as an IPFS implementation in rust, but we broke out & ended up doing our own thing. We're not at the point where the iroh implements "the full IPFS experience" (some parts border on impossible to do while keeping a decentralized promise), but we're getting closer to the "p2p website hosting" use case each week.

if you are looking for something similar to ipfs but a bit more minimalistic and performance oriented, check out iroh https://github.com/n0-computer/iroh .

It is a set of open source libraries for peer to peer networking and content-addressed storage. It is written in rust, but we have bindings to many languages.

One part of iroh is a work in progress implementation of the willow spec. The lower layers include a networking library similar to libp2p and a library for content-addressed storage and replication based on blake3 verified streaming.

Most iroh developers have been active in the ipfs community for many years and have shared similar frustrations... See this talk from me in 2019 :-) https://www.youtube.com/watch?v=Qzu0xtCT-R0

IPFS Protocol Stack: Iroh

We have an initial release out since earlier today: https://github.com/n0-computer/iroh/releases/tag/v0.1.0 but we are still very early, so be gentle :)

(Disclosure: I work for the Filecoin Foundation/Filecoin Foundation for the Decentralized Web).

I do actually agree that the privacy and anonymity aspects of IPFS are not well- conveyed. I think people get hooked on the "censorship-resistant" nature of decentralized systems, without understanding that even if you have multiple sources, for instance in a content-addressable network like IPFS, aggressive censorship systems have other strategies to dissuade dissemination or punish readers. You always have to be thinking a few steps ahead. Services like Tor and, I hope, the IPFS network both try to convey what threat models they are useful for, and which they are not, but it's really hard to stop overenthusiastic re-statements that give them super-powers they do not, in fact, possess.

That said, there's a bunch of careful thinking right now going on about how IPFS's privacy story could be improved: https://blog.ipfs.tech/ipfs-ping-2022-recap/ has a couple of sessions on this, and is a great summary of some other recent developments in the space.

One of those improvements is in the point about nodes being high CPU, RAM, etc. (I actually find this to be more of a challenge when running the full IPFS Go node locally on my desktop, rather than on a VPS; it requires some tweaking.)

The strategy right now is to encourage more implementations of IPFS to cover more use-cases; the original go-ipfs had to do everything, including maintaining some legacy decisions. Nowadays, there's a lot of effort on alternative IPFS implementations that can be slimmer, or optimised for particular scenarios, e.g. on an embedded device, serving a high-load web gateway, or providing millions of files. Protocol Labs recently renamed their canonical go-ipfs to kubo (https://github.com/ipfs/kubo ) to make it more of a peer with other implementations.

Of course, I love all these new generation implementations EQUALLY, but if you pushed me, I've enjoyed playing around with https://github.com/n0-computer/iroh , a modular rust implementation building off the increasingly robust rust libp2p etc libraries. There's some more to pick from here: https://docs.ipfs.tech/basics/ipfs-implementations/

Take a look at GarageS3, it's a niceoption for "just an S3 server" for self hosting.

https://garagehq.deuxfleurs.fr/

I use it for self hosting.

Garage (https://garagehq.deuxfleurs.fr/) gets pretty close for object storage. It’s built with mixing high/low latency links and replication between multiple hosts. Unfortunately it’s not really built for end-users, but devs, so there’s no ui or anything like that.

> Theoretically they could swap with minio but last time we used it it was not a drop-in replacement yet.

Depends on whether AGPL v3 works for you or not (or whether you decide to pay them), I guess: https://min.io/pricing

I've actually been looking for more open alternatives, but haven't found much.

Zenko CloudServer seemed to be somewhat promising, but doesn't seem to be managed very actively: https://github.com/scality/cloudserver/issues/4986 (their Docker images on DockerHub were last updated 10 months ago, which is what the homepage links to; blog doesn't seem active since 2019, forums don't have much going on, despite some action on GitHub still)

There was also Garage, but that one is also AGPL v3: https://garagehq.deuxfleurs.fr/

The closest I got was discovering that SeaweedFS has an S3 compatible mode: https://github.com/seaweedfs/seaweedfs

Ah, you should check out Garage (https://garagehq.deuxfleurs.fr/) for a self-hosted, cluster-y API of S3

I'm a big fan of Garage[1], which is a dead-simple S3 drop-in that you can host on your own drives. It's designed for consumer hardware with shitty internet in-between nodes.

[1]:https://garagehq.deuxfleurs.fr/

One more thing we are also proud of: a bunch of our users is using the object storage Garage, this OSS project looks really promising, and we really cherish the OSS for this kind of unexpected combination.

- Another nice comment seen on HN « it seems to be very easy to run, not very IO intensive, and running fine on a single node with modest hardware with >2 billion log rows. It has a really cool dynamic schema feature too.» [9]

Fun fact: at least 4 users are using Garage[10] as the object storage, this OSS project looks really promising and made the HN front page a few months ago[11], we really cherish the OSS for this kind of unexpected combination.

Any feedback positive/negative always greatly appreciated here!

[0] Quickwit repo: https://github.com/quickwit-oss/quickwit

[1] Searching the web under 1000$/month: https://news.ycombinator.com/item?id=27074481

[2] Chitchat gossip library: https://github.com/quickwit-oss/chitchat

[3] Columnar format: https://github.com/quickwit-oss/tantivy/tree/main/columnar

[4] Tantivy library: https://github.com/quickwit-oss/tantivy/

[5] Whichlang library: https://github.com/quickwit-oss/whichlang

[6] GitHub Archive demo in terminal: https://www.youtube.com/watch?v=SNq3bARRlDI

[7] Indexing performance: https://twitter.com/fulmicoton/status/1638016949459488768

[8] https://twitter.com/arnonrgo/status/1645429632303235073?s=20

[9] https://news.ycombinator.com/item?id=35742544

[10] Garage object storage: https://garagehq.deuxfleurs.fr/

[11] https://news.ycombinator.com/item?id=33853539

On the technical side, garage (https://garagehq.deuxfleurs.fr/) does multi master replication by default, so is probably better for this use case. Still with S3 API.

You are looking for garage.