25C3 was amazing! Thanks to everybody who presented and attended! Especially big thanks to the German Privacy Foundation and the i2p team.
The video of our lightning talk is embedded above. You might not be able to see the slides in the video (that’s what the interrupt is about) so if you want to see the slides you can see them here.
a decentralized trackerless feature was bether i think then a Bittorrent Tracker.
and hope can make bether gui which shows seeded files too
like how in Rufus/G3 client looks?
Rufus/G3 has more advanced gui then the Bittorrent 4.0 Gui.
for Anomos needs the special Tracker software?
That needed before cant start a Tracker for Anomos.
Last Opensource version of Bittorrent 5.2.2
http://download.bittorrent.com/dl/BitTorrent-5.2.2.tar.gz
it has TRackerless feature and more advanced Gui.
Last Bittorrent 5.2.2 opensource version with Trackerless feature:
http://fileload.us/913246253-BitTorrent-5.2.2.tar.gz
Bittorrent.com seems now removed old sources.
But i see it today some hours ago.
I dont see why Anomos need a non-standard tracker. A corresponding “Tracking code” should be able go generate by the peers themselves. This and data transfer performance are cruisal for Anomos success.
Maybe it will be too many failed attempts, timeouts to BitTorrent clients until Anon Torrent take over the market…
Above was a compromise only using intermediate nodes from the swarm but from all standard BitTorrent clients. A simple AI algorithm can find a “tracker code” or route, omitting BitTorrent clients, to the peer.
Correction. Intermediate nodes from ALL the user’s swarms or else it is (empirically) known by everyone what file is relayed.
I think there is a limit here. The whole idea builds on that a node can be only relaying and nothing else. I.e can the info_hash request give some random users by a trick?
Here is the solution intelligent or stupid lifeforms are waiting for: An invincible modification of the BitTorrent tracker for Anon Torrent: Give info_hash a null value and the tracker returns a random BitTorrent swarm… A simple AI algorithm can find a “tracker code†or route, omitting BitTorrent clients, to the peer. (Was on false track in 8 and 9 above)
Just introduce an ‘AnonTorrent’ ping to check for Anon compatible clients from info_hash(NULL). Then make up the “Tracker code” route. This was the AI :) I am almost sure all will accept implementation of this info_hash() return value in all trackers if one claim a need for it…………..who will implement a ‘libAnonTorrent’ and hook it on a ready nade front-end?
(Was very deep thinking in 7 above)
P.S. Dont forget to have intermediate nodes from many swarms so if a peer is intercepted the relayed file at least us unknown. The peer is said to only be relaying, like everybody else in “Anonarcy”…D.S.