Natanael

6 ms·

1.
by Natanael 13y ago
The main reason for that is that software very rarely is properly sandboxed by default.
2.
by Natanael 13y ago
The addresses is a hash of a public key, not a public key itself.
3.
by Natanael 13y ago
Which is why we need to get it studied more.
4.
by Natanael 13y ago
I've never had problems with receiving messages with it. Had I2P been running for at least 20 minutes or so to be able to establish enough connections? Bote can tell you how many Bote nodes it is connected to.
5.
by Natanael 13y ago
@synctext: you can't have traffic anonymity without routing. And I2P is mainly slow because the shared bandwidth is low. Also, it isn't a hard as you claim. It is mainly a matter of setup.
6.
by Natanael 13y ago
Doesn't I2P fit better, considering the design requirements? Tor would require very significant changes to scale better for high volume traffic, but I2P already handles it reasonably well.
7.
by Natanael 13y ago
What do you think of Bote mail in I2P, which uses DHT for relaying mail? It is set to hold mail in the DHT for 100 days or until fetched by the recipient. It also uses public keys as addresses (ECDSA and NTRU are the options), and all mail
8.
by Natanael 13y ago
5460 satoshis is the current default minimum that Bitcoin itself allows (other transactions are valid, but won't be forwarded, thus you need to hand it over to a miner yourself for inclusion in a block).
9.
by Natanael 13y ago
Some allow larger keys. I once generated an 8192 bit key. It took a loooong time. Never used it. I guess that piece of software would have allowed 16k keys too.
10.
by Natanael 13y ago
> If you don't trust Gmail, you shouldn't trust it any less if/when they deploy PGP for it. The problem here might be that people (including Google, I guess) don't want users to trust anything MORE THAN THEY SHOULD, w