IPFS exacerbates one of the world's worst problems

• ResNetLab

  1 100 0.0

  Building resilience into the foundational infrastructure for Human Knowledge

  

We're continuing to build up our latest work and insights on the right replacement here: https://github.com/protocol/ResNetLab/blob/master/OPEN_PROBLEMS/ROUTING_AT_SCALE.md and there's an open RFP for a better routing design here: https://github.com/protocol/research-RFPs/blob/master/RFPs/rfp-7-MLDHT.md

• Go IPFS

  63 13,905 9.6 Go

  Discontinued IPFS implementation in Go [Moved to: https://github.com/ipfs/kubo]

  

I don't know what the op means here, but if the implication is that it's easier for big users to get data accessible via the DHT than small users then ironically this is completely backwards. Any user (who has a publicly reachable IP address or if NAT'd have UPnP or manual port forwarding) can do ipfs init; ipfs daemon; ipfs add myFile wait a couple minutes and then other users will be able to find the data in seconds. As mentioned above the biggest problems with the current IPFS public DHT based content discovery start creeping in when people want to add larger data sets. Given that the main issue is how many CIDs you are providing/telling people about there are various options available including manually providing with ipfs dht provide or https://github.com/ipfs/go-ipfs/blob/master/docs/config.md#reprovider.

• WorkOS

  workos.com featured

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

Suggest a related project