3 ms·

Interesting, I have something like this on my "perhaps I should do that" list. From the protocol description it seems, that one shares a torrent file (with the

by yk 13y ago

Interesting, I have something like this on my "perhaps I should do that" list. From the protocol description it seems, that one shares a torrent file (with the profile) to the followers over i2p? And this torrent is signed with DSA-SHA1, to provide the authenticity of the profile? ( At least I think this should be the idea in a very handwaving way? I am not really sure how much I did understand.) And two give a little bit of feedback: 1. Nightweb is 'calling home' via the latest.js. ( This information should probably better be shared via i2p, since this is at least leaking, who is running Nightweb.) 2. Some tutorial or at least tooltips. At least I do not really understand the UI at the moment. 3. I was finally able to understand what to do with a .jar file, and that Java wants to be called with -jar, I am not really sure if the average user knows, what he should do with a .jar without further explanation. Edit: How long should it take to spread a new posting through the network? ( I am wondering if something like chat/twitter could be done through NW.)

gw 13y ago
Your description of the protocol is basically right. All metadata is shared in a torrent called a "meta torrent", which you get via other users as a signed infohash. After querying for the torrent over the DHT network, you begin downloading the files. You are right that the update checking system is pretty crude right now. I definitely plan on eventually updating over I2P. I will probably wait until I have implemented generic file-sharing and just piggy-back on that functionality to distribute updates. I plan on adding a welcome message that explains how to use the interface. I already have that in the Android version, but for whatever reason I skipped over it this time. I think on Windows and OS X, you can just double-click a JAR file and it will launch it with Java. Hopefully most users won't have to drop to the command line to run it. Right now it's quite slow to get an update -- especially when you are getting their metadata for the first time, which can take 5 minutes or more sometimes. I plan on working really hard to speed this up over the next few months.
- yk 13y ago
  Thanks for the answers. And I did wonder, if you plan to implement something like groups? ( As far as I understand, this would be something like sharing a private key.)

by yk 13y ago

gw 13y ago

Your description of the protocol is basically right. All metadata is shared in a torrent called a "meta torrent", which you get via other users as a signed infohash. After querying for the torrent over the DHT network, you begin downloading the files. You are right that the update checking system is pretty crude right now. I definitely plan on eventually updating over I2P. I will probably wait until I have implemented generic file-sharing and just piggy-back on that functionality to distribute updates. I plan on adding a welcome message that explains how to use the interface. I already have that in the Android version, but for whatever reason I skipped over it this time. I think on Windows and OS X, you can just double-click a JAR file and it will launch it with Java. Hopefully most users won't have to drop to the command line to run it. Right now it's quite slow to get an update -- especially when you are getting their metadata for the first time, which can take 5 minutes or more sometimes. I plan on working really hard to speed this up over the next few months.

yk 13y ago
Thanks for the answers. And I did wonder, if you plan to implement something like groups? ( As far as I understand, this would be something like sharing a private key.)