3 ms·

In your previous submission you hinted at multiprotocol support, mainly for IPFS, but I don't see that here -- only references to the Dat protocol. Did that eff

by niftich 10y ago

In your previous submission you hinted at multiprotocol support, mainly for IPFS, but I don't see that here -- only references to the Dat protocol. Did that effort get cancelled or am I just not finding the info? When you say you use (among others) 'Kademlia Mainline Distributed Hash' for discovery, are you referring to the Mainline BitTorrent DHT, or just a different instance of it, operating on the same principles? How are you resilient against sybil attacks? Did you end up forking Electron?

snowpalmer 10y ago
I was curious about IPFS support as well. The docs mention it near the bottom: https://beakerbrowser.com/docs/index.html https://beakerbrowser.com/docs/index.html Sounds like you need the IPFS daemon running for it to work.
pfraze 10y ago
Good questions > Did that effort get cancelled or am I just not finding the info? I've paired the focus down to Dat, yes. IPFS is still supported but Dat's my main focus. I may write a post later. > the Mainline BitTorrent DHT, or just a different instance of it, operating on the same principles? Yes, the Mainline DHT. > How are you resilient against sybil attacks? Dat sites are singly-owned and signed by private keys. The DHT network has all the same issues that BitTorrent has always had [1]. We use fallback networks that are less distributed (a custom DNS server) but we'll need to evolve that solution > Did you end up forking Electron? No, thankfully! I've been working with GitHub via PRs. They added the feature most needed so far, proper process-level sandboxing, so hopefully a fork won't be necessary. 1 https://security.stackexchange.com/questions/80933/how-can-the-sybil-attack-be-used-on-a-p2p-system-that-implements-dht https://security.stackexchange.com/questions/80933/how-can-t...
- wesleytodd 10y ago
  > No, thankfully! I've been working with GitHub via PRs. They added the feature most needed so far, proper process-level sandboxing, so hopefully a fork won't be necessary. Do you have a link to the issue where this was fixed/discussed? I searched for it last week and couldn't find it.

by niftich 10y ago

snowpalmer 10y ago

I was curious about IPFS support as well. The docs mention it near the bottom: https://beakerbrowser.com/docs/index.html https://beakerbrowser.com/docs/index.html Sounds like you need the IPFS daemon running for it to work.

pfraze 10y ago

Good questions > Did that effort get cancelled or am I just not finding the info? I've paired the focus down to Dat, yes. IPFS is still supported but Dat's my main focus. I may write a post later. > the Mainline BitTorrent DHT, or just a different instance of it, operating on the same principles? Yes, the Mainline DHT. > How are you resilient against sybil attacks? Dat sites are singly-owned and signed by private keys. The DHT network has all the same issues that BitTorrent has always had [1]. We use fallback networks that are less distributed (a custom DNS server) but we'll need to evolve that solution > Did you end up forking Electron? No, thankfully! I've been working with GitHub via PRs. They added the feature most needed so far, proper process-level sandboxing, so hopefully a fork won't be necessary. 1 https://security.stackexchange.com/questions/80933/how-can-the-sybil-attack-be-used-on-a-p2p-system-that-implements-dht https://security.stackexchange.com/questions/80933/how-can-t...

wesleytodd 10y ago
> No, thankfully! I've been working with GitHub via PRs. They added the feature most needed so far, proper process-level sandboxing, so hopefully a fork won't be necessary. Do you have a link to the issue where this was fixed/discussed? I searched for it last week and couldn't find it.