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

IPFS Maintainers Winding Down

ipshipyard.com

Post reply on HN
Print view View original

151–160 of 226 posts

Re: IPFS Maintainers Winding Down

#151

Post by fc417fc802 »

jazzyjackson wrote: post #102
gwerbin wrote: post #77

Earlier quoted context omitted.

What's silly about it? Content-addressable decentralized storage -- not tied to a cryptocurrency -- is really valuable for censorship-resistant archiving of politically-sensitive data (such as climate change research).

Except it wasn’t censorship resistant at all, in that your node advertised itself as a node with a-z files on it. Separately you could put it behind a vpn or run a vps you paid for with monero, but fundamentally it’s more of a way just to pin a file to an address that works no matter what domain or IP the file is behind.

Censorship resistant in the same sense that bittorrent is, with no single centralized server or domain registration to target.

Re: IPFS Maintainers Winding Down

#152

Post by spockz »

crest wrote: post #86
muragekibicho wrote: post #73

Earlier quoted context omitted.

I guess IPFS is an artifact from the crypto craze. It's pretty silly if you think of it. However, I must admit, I got my first ever developer grant from Filecoin while they were flush with ZIRP era money. btw,I thought it was an Initial Coin Offering, not an actual fundraise.

What people did or planned to do with IPFS is pretty silly, but the idea of content addressed storage with cryptographic (not in a crypo coin way) names makes a lot of sense. It would make for a great software distribution method e.g. your game downloads get faster the more people want to play the latest version. It's the combination of Git and BitTorrent and has uses far beyond just hosting warez and NFTs.

This. I also always imagined it be able to host some version of an Encarta/encyclopedia that would be so distributed it would probably survive world wide catastrophe.

Re: IPFS Maintainers Winding Down

#153

Post by ErroneousBosh »

embedding-shape wrote: post #106
ErroneousBosh wrote: post #38

Earlier quoted context omitted.

Why do you need Tailscale? Edit: Okay, so a couple of people have downvoted but no-one has answered. Why would you use tailscale to secure a web app?

I think parent is talking strictly about P2P, so you'll need (typically) something to help you tunnel between clients, as there are NATs and all sorts of things between two typical consumer computer at two different homes.

Ah, okay, but that sounds like an incredible pain in the arse to do no matter how you approach it.

Re: IPFS Maintainers Winding Down

#154

Post by zaik »

sunshine-o wrote: post #113

The question is why IPFS did not get the traction something like Tor had for decades? I believe the fundamental problem of those protocols is everyone fear ending up serving child porn just by running a "node" and taking a chance at explaining the future P2P internet to a judge. IPFS got a CID deny list [0] but it was too little too late - [0] https://badbits.dwebops.pub/

Other nodes cannot make you host arbitrary content you did not request yourself.

Re: IPFS Maintainers Winding Down

#155

Post by sunshine-o »

zaik wrote: post #154
sunshine-o wrote: post #113

The question is why IPFS did not get the traction something like Tor had for decades? I believe the fundamental problem of those protocols is everyone fear ending up serving child porn just by running a "node" and taking a chance at explaining the future P2P internet to a judge. IPFS got a CID deny list [0] but it was too little too late - [0] https://badbits.dwebops.pub/

Other nodes cannot make you host arbitrary content you did not request yourself.

I was talking about running a public IPFS gateway. This is what the deny list is for.

Re: IPFS Maintainers Winding Down

#156

Post by sadclown42 »

momack2 wrote: post #119

The post here is pretty confusing (so no blame to anyone who reads this as "IPFS the project" shutting down instead of just a single maintainer team, it's totally misleading) - but this is actually just a sunset announcement for _Shipyard_ - one of many IPFS implementation maintainers. *The IPFS Project is not sunsetting or shutting down* - just switching to individual maintainer grants instead of centralized impleme…

"Just switching to individual maintainer grants" implies a switch that has been planned. Protocol Labs made this call, so the timeline was not a surprise to them.

In November 2023 Protocol Labs published a plan for exactly this situation: independent foundations, IP transferred out of Protocol Labs, the IPFS and libp2p teams becoming independent entities, and public goods funds that Protocol Labs made "a major pledge" to. https://pl.xyz/blog/advancing-ipfs-and-libp2p-governance/

Three years on, the entity those maintainers formed is winding down because that funding was not renewed, and the most detailed public account of what replaces it is a comment in this thread. pl.xyz still says Protocol Labs "continues to support those projects".

Shipyard's last day is September 30. Can you name who holds Kubo, Boxo and Helia on October 1? Not the funding mechanism, the people: who has commit and release rights, who receives an embargoed vulnerability report, and who decides when a fix ships. A grant that has not been awarded yet is a plan to make a plan.

Same for "one of many IPFS implementation maintainers". Which other team ships Kubo, Boxo or Helia? Iroh is a separate project, not a second maintainer of these.

These questions are already on the forum and unanswered: https://discuss.ipfs.tech/t/what-happens-to-ipfs-maintenance...

Re: IPFS Maintainers Winding Down

#158

Post by stavros »

jadbox wrote: post #49
devttyeu wrote: post #4

Sad to see it go having been a maintainer some years ago. For anyone wondering, there are more sustainable (with a viable, focused business backing the project) options to do p2p, namely Iroh - https://www.iroh.computer/ which was built by ex-IPFS ex-Protocol Labs devs (I have no relation to the team beyond having worked with them back in the day). Sadly Protocol Labs is doing.. ehh whatever now, except apparently su…

who uses Iroh?

I really wish Moonlight would use Iroh. I use Tailscale to make it work, but it would be so much easier to just pair a machine and have it always work.

Re: IPFS Maintainers Winding Down

#160

Post by superb_dev »

iand wrote: post #149
jubilanti wrote: post #141

Earlier quoted context omitted.

@dang yes, and title is editorialized, the real one is "The end of IPFS at Shipyard" which is more informative It's still a a real loss, those are widely used products, but the signal that Protocol Labs is sending about IPFS in defunding this might be even worse for the ecosystem. Cloudflare, Brave, and now Protocol Labs have abandoned it.

Except no-one knows what shipyard is and it could more easily be mistaken for the end of IPFS. Maintainers of IPFS are winding down is much more informative for those not in the space.

I think it’s easy to infer from that title that “shipyard” is an individual project or organization and not IPFS as a whole
Post reply on HN