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.
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.
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?
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.