postman.i2p only permits torrents which includes its tracker in the torrent file, which means popular torrents from 1337x, TPB et al can't be uploaded there (at least not without changing the infohash). Torrent clients like qBittorrent and BiglyBT can cross-seed on I2P and clearnet networks which is a recent development since libtorrent 2.0 came out (software packages take a while to bump to.the latest library), but from what I've tested nearly all of the infohashes I put into my client from "clearnet" torrent sites have stalled, probably because I2P is a little too bespoke at the moment.

The potential is definitely there IMO, but unless you're just watching mainstream movies and TV it's not a replacement for clearnet/VPN.

If I'm missing something I'd like to know :)

[–] onlinepersona@programming.dev 3 points 5 months ago (1 children)

The info hash shouldn't change as per spec.

info_hash

The 20 byte sha1 hash of the bencoded form of the info value from the metainfo file. This value will almost certainly have to be escaped.

The info value is a separate key of a torrent file

metainfo files

Metainfo files (also known as .torrent files) are bencoded dictionaries with the following keys:

announce
The URL of the tracker.
info
This maps to a dictionary, with keys described below.

The info dictionary does not include the list of trackers, therefore the infohash shouldn't change.

The most likely reason your torrent stalls when running in I2P mode is probably that it doesn't exist on the tracker.

Anti Commercial-AI license

[–] theroff@aussie.zone 2 points 5 months ago

I stand corrected, thank you. I'll have to try that out.

load more comments (14 replies)