"sutld", or "alt-tld" on their ML viewer [0] and reading
the (extensive) back-history of these discussions. See below for a link
to my earlier comments on this tor-dev thread [1], as well as several
IETF drafts you may wish to read and comment on [2-3].
Cheers,
str4d
[0] https://
, should they try *.foo in the DNS? The
browser either needs to know the full contents of *.alt (which is not
possibly because by design it will have no official registration), or
every registered TLD in DNS (which won't ever be added as a restriction
because of various legacy local-net vendo
as I2P-only peers can only reach the bridging nodes,
whereas Tor-only peers can connect to clearnet Namecoin nodes too
(although as with Bitcoin there is the issue of exit node traffic
manipulation).
str4d
[0] https://github.com/bitcoin/bitcoin/issues/2091
[1] https://github.com/VirtualDestructor/bitcoin-qt-i2p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
str4d wrote:
> Vasilios Mavroudis wrote:
>> Hello,
>
>> I would like to introduce our project "Crux", which enables the
>> computation of privacy preserving statistics on sensitive data.
>> The project wa
and would provide
noticeable benefits (making blanket bans much harder).
str4d
[0] http://zzz.i2p/topics/1577-ntcp2
[1] https://moderncrypto.org/mail-archive/curves/2014/000151.html
[2] https://moderncrypto.org/mail-archive/curves/2014/000163.html
[3]
https://github.com/i2p/i2p.i2p/blob/master/rout
nknown risks. As such forwarding can be done most
> safely by Tor itself, the Tor Project reserves the right to
> forward CNAME records between NameService lines in the future.
> Applications should therefore not depend upon the above error
> being returned.
One thing that the I2
of several thousand. It therefore
also helps to mitigate DDoS attacks (although the biggest of services
e.g. Facebook would likely have their own systems that would better
handle this).
str4d
___ tor-dev mailing
list tor-dev@lists.torproject.org
trying to make this stuff understandable to end
users (usability and UX of the tools themselves aside), without having
multiple kinda-similar-but-not tools trying to do so in different
ways. A united concept front would benefit tools _and_ users.
str4d
[0] http://zzz.i2p/topics/1780-hidden-services
.
Alternatively, rebase the system on I2P.
If they did choose to rebase on I2P, they would be able to integrate
with the existing I2P torrent swarms. In case the Tribler developers
are following this ML, the protocol details common to all BitTorrent
clients on I2P are documented in [1].
str4d
[0] https
this further if anyone is
interested, because a combined / general approach would benefit
multiple networks.
str4d
[0] https://geti2p.net/en/docs/discussions/naming
[1] http://zzz.i2p/topics/1545 (in I2P)
[2] http://trac.i2p2.de/wiki/GNS
-BEGIN PGP SIGNATURE
-research-framework and use the
Java crypto in the Python code. See Jy2P [0] for an example, it uses
Jython to start the Java I2P router and run Python code to interact
with it.
str4d
[0] https://github.com/majestrate/jy2p
___ tor-dev mailing
list tor-dev
the
Orchid codebase as part of their plan to bundle it by default[3].
str4d
[0]: https://github.com/subgraph/Orchid
[1]: http://plugins.i2p.me/plugins/orchid/ (via I2P inproxy)
[2]: https://github.com/str4d/Orchid
[3]: https://github.com/bitcoinj/bitcoinj/pull/28
-BEGIN PGP SIGNATURE
to benefit).
str4d
zw
___ tor-dev mailing
list tor-dev@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.14 (GNU/Linux)
iQEcBAEBCgAGBQJS/f
13 matches
Mail list logo
