danoctavian

4 ms·

1. 1.▲
   by danoctavian 11y ago

   What is your domain?
2. 2.▲
   by danoctavian 11y ago

   That's a good point. You still need those. I don't believe there's any way around it whenever you're using a decentralized network like the DHT, you need to somehow "get into" the network, so you need to know s
3. 3.▲
   by danoctavian 11y ago

   It's not production ready, it's quite flaky because of the NAT penetration. it sometimes works, sometimes doesn't. It's a POC, i don't have the bandwidth now to make it robust.It's meant to showcase it's p
4. 4.▲
   by danoctavian 11y ago

   Well BitTorrent's own project Bleep uses the Bittorrent network as well. Their protocol is more complex however. Their goals are to hide who is talking who, from entities that might just be scraping the DHT. With bluntly, you can tell
5. 5.▲
   by danoctavian 11y ago

   proof of concept code for making secure connections between 2 peers by knowing only each other's public keys. (no servers or IP knowledge involved, featuring NAT penetration). uses the bittorrent DHT. code is hacky, written for fun. As
6. 6.▲
   Bluntly: Serverless, NAT-breaking P2P with public keys and BitTorrent DHT(github.com)

   58 points by danoctavian 11y ago|16 comments