ev on Nostr: I'm not sure what my comments would be yet. I wish I knew what was right and/or wrong ...
I'm not sure what my comments would be yet. I wish I knew what was right and/or wrong around decentralized blob sharing.
I do agree with you guys that IPFS is heavy and BitTorrent has weird compability issues between the WebTorrent and Desktop clients.
With IPFS you always run into the issues where no one is pinning the blob, so you gotta keep a node on otherwise no one else can access it.
One of the things I liked about Scuttlebot's blob distribution system was you could nearly assume your friends had the blob, which made it easy to retrieve.
Nostr doesn't have a replication strategy, and all of the peers aren't assumed to hold the posts and blobs, so how does this need to be handled?
I don't know what the right answer is yet.
For distributed Git, you need all of the blobs from all of the commits to clone a full repo though, so that's something to consider if we're trying for a `git-ssb` do-over on Nostr.
`git-ssb` only ran into issues when the development team started blocking each other.
I do agree with you guys that IPFS is heavy and BitTorrent has weird compability issues between the WebTorrent and Desktop clients.
With IPFS you always run into the issues where no one is pinning the blob, so you gotta keep a node on otherwise no one else can access it.
One of the things I liked about Scuttlebot's blob distribution system was you could nearly assume your friends had the blob, which made it easy to retrieve.
Nostr doesn't have a replication strategy, and all of the peers aren't assumed to hold the posts and blobs, so how does this need to be handled?
I don't know what the right answer is yet.
For distributed Git, you need all of the blobs from all of the commits to clone a full repo though, so that's something to consider if we're trying for a `git-ssb` do-over on Nostr.
`git-ssb` only ran into issues when the development team started blocking each other.