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

171–180 of 226 posts

Re: IPFS Maintainers Winding Down

#171

Post by anacrolix »

gritzko wrote: post #18

I can not say IPFS was a bad idea. Consider GitHub: it is a massive content-addressed store with a smiley on it. There has been some very hot P2P products, e.g. Tailscale. Protocol Labs had its peak during/after the ICO, but long-term, (1) they did not focus on some particular audience and (2) performance of the network was not great. I personally believe that their bet on DHT was not the right one (I worked in this…

I worked on their DHT and it was broken from the start, and they didn't want to hear how to fix it. What would I know.

Re: IPFS Maintainers Winding Down

#172

Post by int_19h »

runarberg wrote: post #17
mikert89 wrote: post #12

Does IPFS actually have users? I remeber when they raised 270 million and a bunch of people there got wildly wealthy

Wait are you telling me yet another supposedly ground breaking technology turned out to be yet another grift. I know a lot of people on HN are going to call me overly cynical. But this pattern should be so obvious by now. Any cynicism to any new ground breaking technology which is gonna solve a problem that exists because of capitalism, that this cynicism is more than warranted. At this point we should all be cynical…

New technology has always benefitted first and foremost those in power, simply because people who get to extract wealth from the rest of society can then direct that wealth to acquire new tech first. This was equally true in pre-capitalist societies, or in USSR for that matter.

Being cynical about the tech itself is a bridge to nowhere, though, because it does not preclude its existence or usage, it just cuts you away from any benefits that you can personally get out of it - but you're still affected by all the downsides.

Don't be cynical about tech. Be angry at the people who want to own it all and use it to exploit you.

Re: IPFS Maintainers Winding Down

#173

Post by dannyw »

arccy wrote: post #140
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…

one of many, or the main maintainers? seems like they run a lot of the well known public infra too.

Shipyard has been one of the main maintainers because they have previously been an aggregator of funding — think consulting firm, that gets grants and hires people.

Protocol Labs is moving and offering to pay (as far as I understand) the same maintainers and developers directly; just not via Shipyard.

Re: IPFS Maintainers Winding Down

#174

Post by cchance »

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…

Shipyards shtting down not IPFS, the title is editorialied

Re: IPFS Maintainers Winding Down

#175

Post by AyyEye »

arjie wrote: post #111
JuniperMesos wrote: post #48

> If you have a favourite memory of working with Shipyard, or an idea you always hoped IPFS would eventually achieve, we’d love to hear it. Google Form One important thing I'd like to see IPFS or a similar decentralized web technology achieve, is getting rid of the necessity of filling out a Google form in order to tell the Shipyard people what I think about their maintenance of IPFS. Seriously it bugs me when people…

I wonder what distinguishes these kinds of communities over others. Some, like 'decentralization' or 'privacy' or 'security', require absolute adherence. If you're building a decentralized tool or a privacy tool or a security tool you must first reinvent the universe. Post on HN? Centralized, privacy nightmare, insecure. Use Gmail as your email provider? Centralized, privacy nightmare, insecure. Fastmail? Centralized…

Making a google form requires more effort than "send me an email at mailto://feedback@shipyard.com". The email body can even be prepopulated with the feedback template. Its really not a high bar, and thus disheartening that the people that should care, seemingly, dont.

Re: IPFS Maintainers Winding Down

#176

Post by nailer »

muragekibicho wrote: post #73
mikert89 wrote: post #12

Does IPFS actually have users? I remeber when they raised 270 million and a bunch of people there got wildly wealthy

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.

> btw, I thought it was an Initial Coin Offering, not an actual fundraise.

An ICO is a type of fundraise.

Re: IPFS Maintainers Winding Down

#177

Post by stackghost »

chriswarbo wrote: post #170
stackghost wrote: post #167

Earlier quoted context omitted.

The number of normies visiting urls directly from a CDN is a rounding error. Non technical users like pronounceable domain names. It's why we aren't just using IP addresses. CAS is intimidating to non-technical types.

Pronounceable names can point to a content address, the same way they can point to an IP address. For example, https://dnslink.dev points a DNS name to a content address; git refs point to git objects; etc.

This is irrelevant. The point I'm responding to is this:

>I think something like IPFS is definitely needed. There is nothing stopping you from distributing a webapp on bittorrent but you'll also need to add a README for instructions on how to run the webapp on localhost so a browser can render it. So thats not something that any non-technical user wants to do.

This quoted comment assumes there's a web app that is sufficiently complex as to require a readme to run it, but that's too complex for normal people.

But somehow, a link that looks like `ipfs://12340-9q5ui1j2;lk3rjq;ladksfj` won't scare those same people off?

Color me extremely skeptical.

Re: IPFS Maintainers Winding Down

#178

Post by 8cvor6j844qw_d6 »

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've seen some product prototypes using Iroh and it appears pretty good for "just get edge device / node connectivity to work" when you don't want end users to bother with networking shenanigans but can guarantee Internet connectivity.

Basically Tailscale but embedded into the app without the hassle of requiring users to setup accounts.

Re: IPFS Maintainers Winding Down

#180

Post by tcoff91 »

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…

Iroh looks so incredibly exciting, I can't wait to play with it.
Post reply on HN