ts-odd VS Go IPFS

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

nice/renice isn’t what it used to be[0].

Bandwidth limiting is not built in[1].

[0] - https://stackoverflow.com/questions/10342470/process-nicenes...

[1] - https://github.com/ipfs/go-ipfs/issues/3065

For me, https://github.com/ipfs/go-ipfs/issues/9044 is the main blocker atm and https://github.com/ipfs/go-ipfs/issues/2167 is still around and annoying.

It makes me wonder if you use the IPFS FUSE mount and symlink an IPNS address of files that you want to sync if it would be read by Dropbox.

I'm using the IPFS fuse mount to load mine into Plex/Jellyfin. It's nice that I can load a movie into a virtual directory on IPFS and my home and remote servers get updated automatically. (when I update my IPNS) So you could run an official solidaritycinema IPNS address that people load into their Plex as a library.

Maybe tangentially related, I've been interested in IPFS as a network medium. ( Using the IPFS fuse mount ) Rather than syncing the entire file it syncs the Library list. When the Plex server makes the request for the file, IPFS negotiates the download. It makes it more like Netflix.

I've been messing with Plex + IPFS and I think it's pretty cool. The IPFS FUSE Mount gives IPFS network access to Plex as just a regular filesystem. To keep it private within my family I'm using a Private Swarm.

"Implement bandwidth limiting" https://github.com/ipfs/go-ipfs/issues/3065

Going on six years now. You can use external tools (like "trickle") or your OS knobs.

So my plan is to setup plex on a relative's Raspberry Pi so that it works off the IPFS mounted network directories in the same way. They'll have a virtual library that takes basically no memory on their Pi unless they request a video, then it'll start caching to their machine.