Different torrent file naming rules in Snark vs. trackers

[jogger]

Currently snark generates torrent file names that might not be accepted by the listed default trackers. One example: Data file name contains a vertical bar "|". Postman will not accept the torrent. I don´t know who is violating the docs.

If the user in this situation renames the torrent file, snark counts this as deletion and subsequent addition. Due to the problematic "preserveFileNames" feature the torrent data structure is now duplicated - potentially filling the disk and crashing the system.

There is no clue for users that the only workaround is to rename the data first and then generate a new torrent file.

[zzz]

I don't think there are any docs that specify what's valid. If there are, please provide a link. You could open a ticket on postman to ask him what his rules are.

[zzz]

could be a windows issue, or he's implemented restrictions to assure compatibility for windows users. '|' is disallowed in windows filenames: ​https://msdn.microsoft.com/en-us/library/aa365247(VS.85).aspx

[slumlord]

Related to I2PSnark naming limits,

I've had problems with I2PSnark (as far as I could tell from my limited investigation, anyways) disliking certain characters in torrent file names.

I vaguely recall that curly brackets are not permitted {}
I deleted the torrent, changed the directory name to remove the brackets, regenerated the torrent with mktorrent and i2psnark accepted the new torrent.

I don't know if Postman's tracker accepts {} in file/directory names but I know I2PSnark will not.