m0xEE on Nostr: Transmission Bittorrent software 4.0.6 has this "tracker flooding issue" on dual ...
Transmission Bittorrent software 4.0.6 has this "tracker flooding issue" on dual stack systems having both IPv4 and IPv6 connectivity — it keeps making requests when tracker url isn't reachable on either of its addresses.
https://github.com/transmission/transmission/issues/7078Some trackers go as far as banning 4.0.6 explicitly. Okay, so I build older 4.0.5 and downgrade to it…
The issue gets a fix, but no version gets released with the fix. Until one day 4.1.0 gets released — and I update a bunch of libraries it depends on, so that won't have to touch it in the near future and just let it be…
Turns out it still has the issue — and the code causing the issue was contributed by the exact same person as the last time 🤦
https://github.com/transmission/transmission/pull/8631It's not as bad as 4.0.6, but it can't be considered a proper fix, and considering it a long-term version to upgrade to might not be the best idea!
FFS, the poor 32-bit 1,5 GHz PowerPC machine with only a gigabyte of RAM on which this instance is hosted had to build all those libraries in vain 😩
Published at
2026-03-14 20:32:05 UTCEvent JSON
{
"id": "bed2691933c5484dc07ed2dc31ce4163f7937e35e18c453b0a4755dd7761fad7",
"pubkey": "f2ef729f1f65cca1cd5e6a049283e9f007dd7c4ec73e3f1f537fcc9540ea558d",
"created_at": 1773520325,
"kind": 1,
"tags": [
[
"imeta",
"url https://nosh0b10.m0xee.net/m0xEE/s/post-0c3d25d0f93d2524df5aaee7492e1724.png",
"m image/png"
],
[
"proxy",
"https://nosh0b10.m0xee.net/m0xEE/p/1773520325.145872",
"web"
],
[
"proxy",
"https://nosh0b10.m0xee.net/m0xEE/p/1773520325.145872",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://nosh0b10.m0xee.net/m0xEE/p/1773520325.145872",
"pink.momostr"
],
[
"-"
]
],
"content": "Transmission Bittorrent software 4.0.6 has this \"tracker flooding issue\" on dual stack systems having both IPv4 and IPv6 connectivity — it keeps making requests when tracker url isn't reachable on either of its addresses.\nhttps://github.com/transmission/transmission/issues/7078\n\nSome trackers go as far as banning 4.0.6 explicitly. Okay, so I build older 4.0.5 and downgrade to it…\n\nThe issue gets a fix, but no version gets released with the fix. Until one day 4.1.0 gets released — and I update a bunch of libraries it depends on, so that won't have to touch it in the near future and just let it be…\n\nTurns out it still has the issue — and the code causing the issue was contributed by the exact same person as the last time 🤦\nhttps://github.com/transmission/transmission/pull/8631\nIt's not as bad as 4.0.6, but it can't be considered a proper fix, and considering it a long-term version to upgrade to might not be the best idea!\n\nFFS, the poor 32-bit 1,5 GHz PowerPC machine with only a gigabyte of RAM on which this instance is hosted had to build all those libraries in vain 😩\nhttps://nosh0b10.m0xee.net/m0xEE/s/post-0c3d25d0f93d2524df5aaee7492e1724.png\n",
"sig": "c0e9ee77ce3498819f07a3ab67854dc396dc8b4c53d7b0308a91886c65c433e38f2b81c7768847cee934b55a6300bf313ba2c202c8ff66d908c054043065faf7"
}
