You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently launched βtracker - BitTorrent web-aggregator with the peers scrape feature.
Build-in scraper is using UDP protocol, to update the peers from LOCAL tracker.
Thoughts: should I really use the 127.0.0.1 address for these requests, or can I simply define the local 0200::/7 one? Will it not route the packets over the public peers? I have just experimentally launched the instance configured to the 0200::/7 tracker, which is running on localhost, and it seems to be as fast as if I were connecting directly to 127.0.0.1.
Here is the online instance, btw:
http://[302:68d0:f0d5:b88d::fdb]
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi there!
I recently launched βtracker - BitTorrent web-aggregator with the peers scrape feature.
Build-in scraper is using UDP protocol, to update the peers from LOCAL tracker.
Thoughts: should I really use the
127.0.0.1
address for these requests, or can I simply define the local0200::/7
one? Will it not route the packets over the public peers? I have just experimentally launched the instance configured to the0200::/7
tracker, which is running on localhost, and it seems to be as fast as if I were connecting directly to127.0.0.1
.Here is the online instance, btw:
http://[302:68d0:f0d5:b88d::fdb]
Beta Was this translation helpful? Give feedback.
All reactions