Is anyone aware of where IPFS community discussion is taking place? The forum seems almost dead and the community page has broken discord and matrix links.

I hope this doesn't signal the decline of ipfs overall. I really would like to see an internet where content addressed routing is a thing.

What makes/made IPFS special was how it could be seen with relative ease on the standard internet. That feature allowed it to bypass censorship. I cannot say I am surprised that the funding was not re-upped since it seems like the modern web really loves censoring the crap out of things.

Edited: I also liked how it bypassed the traditional domain system.

If you are a believer in projects like IPFS and want to work on it full time, email me.

We are building systems that live in the same space as projects like IPFS, Secure Scuttlebutt, Automerge, Tailscale, etc.

For folks who are already experts in this space, able to come in and hit the ground running, remote is an option.

For high growth folks, we have in-person in Austin.

For folks w/ a U.S. security clearance - we have in-person in DC.

has protocol labs itself made any kind of announcement? i don't see anything on the blog

Always found ipfs and the whole "web 3.0" company to be incredibly obtuse to work with especially compared to previous peer to peer networks like bit-torrent.

I could never shake the feeling there is an unnecessary layer of grift embedded in all the protocols.

Kubo is absolutly amazing, is there a group of people interested in keeping kubo alive? If so I'd love to join that conversation

I tried to query a lot of resources (NFT images, many of which are/were hosted on IPFS) from IPFS myself using the official Go server, running on some pretty fast/wide hardware, for a good part of 2021 and 2022. It was a dumpster fire. Here are two specific problems that I remember, though I ran into several more. First, the UDP storm that it created somehow broke my network, where all of my switches gave up and just started sending all of its traffic to all of the nodes on the network. That could have been a "me" thing but it really made it hard to trust. I ended up having to give that server its own VLAN. Second, the caching was brain dead. By default, it would write every resource to the cache even if I was just using it to download them to a local directory, so it wrote everything twice. Even worse, when the cache was full, it would just drop the whole cache, which created huge spikes in IO util. I ended up patching the app to remove caching.

It felt like a really cool demo that never got cleaned up to work as a real production product.

I publish all of my music in ways that are pirate-friendly, which for the moment just means Bit Torrent and IPFS.

See: https://pickipedia.xyz/wiki/Cryptograss:Delivery-kid

If IPFS is starting to wane, does anyone else have a suggestion of a replacement about which I might start to educate my fans?

I wasn't aware of the relationship between Shipyard and Protocol Labs but it looks like Protocol Labs spun out maintenance and development of a lot of core IPFS technology to a new company called Shipyard, with the idea of cordoning off what was a cost center to Protocol Labs, and the hope was that Shipyard would be able to find other sources of revenue beyond the services funding they got from Protocol Labs.

I'm personally quite disappointed because I just built an IPFS based system built on top of Kubo that I was hoping would take off. Now this throws future maintenance of Kubo into question.