|ZeroNet sites may send your data (IP, ...) to the normal internet||in your browser: set a non-working proxy|
|Work on preventing/mitigating XSS and browser fingerprinting.||see poll|
|Your users.json file can't be stored encrypted, and asking for passphrase on ZeroNet start||see bug|
|Use torrents over I2P for anonymity||see bug
see poll, tor/i2p comparison
|ZeroNet source code is at a central place only (github)||see ZeroNet roadmap|
|Site admin are Gods (manipulation, ...)
They decide what code is run from your local HD,
did you fully audit it already?
|Only 8 trackers (SPOF). DDOS (announces to) trackers.
You can add your own tracker, but if no one uses them, you're on your own island
|Even when using --tor always, ZeroNet always connect to a clearnet service
Do not use clearnet port checkers!!! Clearnet port checkers can be compromised!
|I want to revoke ZeroNet's control over the Tor Control Port.
I will manually start an onion service and tell ZeroNet about it.
|Open up a FileServer port only. Let me configure my Tor Hidden Service.||see poll|
|add https||see bug|
|ZeroID||sends your data (IP, ...) into normal internet||
|ZeroBoard||sends your data (IP, ...) into normal internet|
|ZeroPolls||"Votes are tied to your ZeroID, they are pseudonymous, not anonymous.
With a little bit of work someone can find out what you (your ZeroID) voted for."
|You can know when someone sent a mail,
and how many mails he sent.
But, good: you can't know to whom he sent it.
|the proxy operator has access to your data, ID, ...||
|(A)||So you wouldn't be able to delete the source code, and it would be self authenticating,
and you could have an IPNS entry pointing to the latest IPFS link to the source code
|(B)||See my comment about Tor's weaknesses here.|