Blocklists in .gz format

[VladV]

Hello!

In official site I saw that Transmission supports .gzip blocklists put in "blocklists" folder.

Please check if it supports .gz extension too.

I had to unpack blocklist manually to make it work. But if the same .gz is downloaded by Transmission itself, it seems to work well (unpacked and converted to binary). It is about some free lists from ​https://www.iblocklist.com/lists.php

[x190]

Transmission only handles one blocklist url. Any others must be in text format. If you were to properly use the forum for support, we could point you to a script that handles multiple blocklists.

​https://forum.transmissionbt.com/

[x190]

See #4787.

[rb07]

Any others must be in text format.

Not true. Transmission(*) handles any number of blocklists in either format.

I agree that this ticket shouldn't have been created, but disagree that it is a duplicate, the description makes a false assertion, and it has nothing to do with multiple blocklists. The real problem, I'm guessing, is that the user didn't restart (or send a HUP signal to) the deamon or application, which is when the lists are re-created.

(*) By Transmission I mean the daemon, and Tr-Qt. I can't say anything about the other clients since I don't use them. Using "Component: Transmission" is wrong, since it doesn't really say anything.

[x190]

https://trac.transmissionbt.com/wiki/Blocklists#WhatblocklistdoesTransmissionUse

What blocklist does Transmission Use? ¶

Transmission supports the ​P2P Plaintext Format, which is used by PeerGuardian?, Bluetack, Vuze, ProtoWall?, and KTorrent, and the DAT format, which was originally made popular by eMule.

https://trac.transmissionbt.com/wiki/Blocklists#UsingBlocklistsintransmission-daemon

Using Blocklists in transmission-daemon ¶

transmission-daemon doesn't have an "update blocklist" button, so its users have two options. They can either copy blocklists from transmission-gtk's directory to transmission-daemon's directory, or they can download a blocklist by hand, uncompress it, and place it in the daemon's blocklists folder. In both cases, the daemon's settings.json file will need to be edited to set "blocklist-enabled" to "true".

Also in both cases, the daemon is unaware of blocklist updates. Only when it starts it creates new .bin files.

There is a third option: add the blocklist URL in settings.json (only one blocklist is allowed), and use transmission-remote to tell the daemon to update it periodically.

See libtransmission/blocklist.c --- parseLine1() and parseLine2() and also tr_blocklistFileSetContent() and tr_blocklistFileNew() Also, session.c/loadBlocklists(). Either .txt or .gz is okay for the URL used by settings.json or client preferences.

The "Adding Other Blocklists" section of the wiki appears to give misleading information.

[x190]

Re-opening s.t. the Wiki entry can be corrected.

https://trac.transmissionbt.com/wiki/Blocklists#AddingOtherBlocklists

Adding Other Blocklists ¶

Transmission stores blocklists in a folder named blocklists in its configuration folder.

In that directory, files ending in ".bin" are blocklists that Transmission has parsed into a binary format suitable for quick lookups. When transmission starts, it scans this directory for files not ending in ".bin" and tries to parse them. So to add another blocklist, all you have to do is [ADD: uncompress it and] put it in this directory and restart Transmission. [REMOVE: Text and gzip formats are supported.]