FileTransferSelector assumes upload limit is 0 when there's no limit
Background
The HTTPUpload
module's max_file_size
is None
when the stanza doesn't contain the upload file size limit, which is allowed in the the XEP:
an entity SHOULD also include the maximum file size [...] if such a limitation exists
(emphasis mine). Prior to the new upload UI, Gajim handled this None
value correctly, allowing arbitrarily-sized uploads.
The issue
In the new UI code, the None
is treated as 0, here, effectively disabling HTTP upload altogether, forcing JFT fallback.