Our great sponsors
-
WorkOS
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.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
https://siasky.net/ and https://docs.siasky.net/
IPFS has chosen an architecture which fundamentally keeps it non-performant, Skynet is built from the ground up in a different way, and gets 10-100x improvements on performance for content-addressed links, and 100-1000x improvements on performance for dynamic lookups (IPNS)
https://siasky.net/ and https://docs.siasky.net/
IPFS has chosen an architecture which fundamentally keeps it non-performant, Skynet is built from the ground up in a different way, and gets 10-100x improvements on performance for content-addressed links, and 100-1000x improvements on performance for dynamic lookups (IPNS)
I don't know about IPFS but Arweave solved the "permanent" part: https://www.arweave.org/
Peergos is an interesting human-friendly project built on top of IPFS. Works great so far.
Of interest: they provide a trustless way to store your data encrypted data on centralised boxes (S3, Backblaze) if you want.
https://peergos.org/
People hating on IPFS DHT performance probably aren’t using the experimental accelerated DHT client. https://github.com/ipfs/go-ipfs/blob/master/docs/experimenta...
I would have preferred IPFS to do the storage and propagation of data really well and not implemented stuff like IPNS in the core.
To me this should be a separate codebase. And I see this in other features they have been including too.
I'm using IPFS quite heavily to store content generated on https://pollinations.ai but there is no way I could run it without a centralized node that I have control over at the moment because otherwise it would just be painfully slow and unusable.
I have no real use for IPNS at the moment and many of the other features of the core IPFS stack.
Note that the Filecoin network (which was designed to be the incentive layer for IPFS storage) has been operational for some time. If you look at the current status at https://file.app/ , you can see that storage costs there are extremely low for large amounts of data. f you can get your data verified as open, public data by applying for datacap with a Filecoin+ notary, it's currently free. See https://plus.fil.org/ (you can get 32GB of free datacap to play with just for having a github account).
If you want to use the Filecoin network as a "provider of last resort" for IPFS data, there's https://estuary.tech which will mark your data as verified, sort out the deals with storage providers, and then mirror it to IPFS.
There's also third-party tools like https://fission.codes/ , https://docs.textile.io/powergate/ , https://web3.storage/ and https://www.pinata.cloud/ for making this easier.
(Disclosure: I work at the Filecoin Foundation.)
> IPFS is basically the answer to the question "what is the RIGHT way to decentralize the web?"
There is no RIGHT way to decentralize the web. I don't think IPFS is right way to do it either.
Tim Berners-Lee's Solid (https://solid.mit.edu/) offers a much more practical path to a decentralized web. The advantages with Solid's approach over IPFS is that:
- Solid doesn't throw out what we already have, and recommend a new layer on top of the internet. Example: ipns
- Solid handles access control which pretty much every application needs. Encryption is btw, a poor substitute for access control. https://github.com/ipfs/notes/issues/376
- Solid has the ability to revoke access (very important), delete data
- Solid can work in browsers without extensions.
- Solid is not muddied with talk of the Blockchain. It's disappointing that the cryptocurrency has very nearly hijacked this space.
- Solid is conceptually simple. You own a pod that has a unique address (using familiar schemes). You put your stuff on it and allow access to people; like DropBox but standards based. Companies can offer paid hosting services to run your pod - more space, bandwidth etc.
- IPFS is not commercialization friendly.
- IPFS performance is unlikely to be great, ever.
Disclosure: I am invested in an open protocol similar to Solid, but simpler. So not entirely unbiased.
I'll do a Show HN in a month.
Although a reference implementation (https://github.com/webpods-org/podmaster) is kind of ready, there's no documentation yet (which will go up on webpods.org soon).
The only way to see the feature-set is to look at some of the tests. https://github.com/webpods-org/podmaster/blob/master/src/tes...
If you're interested, please email me. I'm looking for collaborators.
Sorry, I don't know when you last tried out IPFS, but IPNS does in fact work: https://docs.ipfs.io/concepts/ipns/
Again, I'm not sure when it wasn't working, or when it began working (it's always worked since I've been around), but IPNS has made huge strides, I use it every day. Even https://ipfs.io is using IPNS, it's very popular.
Related posts
- Remote Plex server and local Plex Server Sync
- Anything similar to StorJ? For self hosted purposes?
- Our own distributed open storage network? A large "Secure" open directory
- Can anyone tell me what IPFS on my Computer does? I really dont understand.
- Filecoin Foundation Successfully Deploys IPFS in Space