notes VS ts-odd

Is there an easy way to comply with an accountable IPFS block list?

"Implement Allow Lists and Block Lists" (2018) https://github.com/ipfs/notes/issues/284

"IPIP 298: (allow|deny)lists for IPFS Nodes and Gateways" (2022)

As for general gateways, those could be used to pull general illegal content against your will, and allow/block lists were discussed at one point for that reason (https://github.com/ipfs/notes/issues/284). However, in the interim, there is a config option Gateway.NoFetch that causes a gateway not to fetch new content, giving you an allowlist if you also have the content you want to share pinned beforehand.

> 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.

This, and a bunch of side issues linked from it, is a good discussion: https://github.com/ipfs/notes/issues/281

IPFS is not anonymous and like other p2p protocols shares your ip address.

There's been a bit of effort to get it working over tor for years now but the fundamental design makes this difficult. Also despite all the money that has poured into filecoin this doesn't seem to be a priority.

This issue is nearly 6 years old:

https://github.com/ipfs/notes/issues/37

As I see, this is an open issue to be implemented natively in IPFS: https://github.com/ipfs/notes/issues/339

Interesting!

Seems to have a fair bit of crossover with what the Fission team is doing. Yesterday I stumbled upon a web page re: a presentation[1] that a key Fission dev/founder (former Ethereum Core Dev) will be making in late September:

I ended up spending some time playing with Fission Drive[2] and looking at their Guide[3], and just generally reading their dev[4] and marketing materials[5].

Anyway, looking at the Web5 site, it seem to strike some of the same notes.

I'm not affiliated with or participating with Fission in any way, but am working as part of a team developing a decentralized storage protocol focused on durability.

[1] https://www.thestrangeloop.com/2022/a-distributed-file-syste...

[2] https://drive.fission.codes/

[3] https://guide.fission.codes/

[4] https://github.com/fission-suite

[5] https://fission.codes/

Currently, I work at fission.codes, and I have to say, it’s right up my alley. I wasn’t expecting to get the job. In fact, I didn’t really take the application seriously. But to my surprise, the CEO reached out to me to schedule a call, which I missed. I was really tired that day, so I slept off. I reached out to the CEO apologizing for missing the call, and trying to reschedule. Thankfully, he did. The interview went smoothly, and I got the job.

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.)

There are several technical affordances to this at the moment. Local-first or edge apps enable the whole experience to take place in the security of one's own device and can continue offline without internet connection. Zero Data protocols like remoteStorage, Fission, and Solidobviate the need to create accounts (because people bring their own data storage) and also enable apps as swappable lenses—"software is the principles of an experience" (as Steve Jobs might have said) and your data becomes the details. Sharing content via URI fragment stores data in the link itself so that no 3rd-party server is necessary to hold the data (for example, a multi-platform music playlist).

You have to encrypt your own files. But there are solutions in the works! In the Filecoin Ecosystem check out https://fission.codes

Check out https://fission.codes they have a private drive

Or check out and the Webnative SDK that we've built all this into: https://github.com/fission-suite/webnative