Author Topic: Report *new* whitelisted client versions | Read the first post!  (Read 18072 times)

Offline batchman

  • Member
  • Posts: 4
Re: Report *new* whitelisted client versions | Read the first post!
« Reply #60 on: November 01, 2016, 05:06:07 pm »
is tixati 2.47 safe to use, since they now announce all time downloaded/uploaded instead of session ones?  :-X

2.47
Quote
- trackers now report all-time upload/download statistics (same as seen in transfer details tab) instead of re-zeroing on every run

Offline SideChain

  • Member
  • Posts: 4
Re: Report *new* whitelisted client versions | Read the first post!
« Reply #61 on: November 02, 2016, 08:02:54 am »
@batchman: Yes. I've just tried it and it worked perfectly fine.

Offline batchman

  • Member
  • Posts: 4
Re: Report *new* whitelisted client versions | Read the first post!
« Reply #62 on: November 02, 2016, 05:19:25 pm »
@batchman: Yes. I've just tried it and it worked perfectly fine.
i dont think so, downloaded 14gb torrent, and through few days of seeding i got these stats on it
Code: [Select]
14.2 GB	415 GB	952 GB	0.436 29.3x
... dont think it was counted towards overall data, still messed up torrent stats pretty badly

i would propose whitelisting version 2.48 as the change was reverted and removing 2.47 (probably even blacklisting it?)

Sorry but you are not allowed to view spoiler contents.
« Last Edit: November 02, 2016, 05:30:52 pm by batchman »

Offline SideChain

  • Member
  • Posts: 4
Re: Report *new* whitelisted client versions | Read the first post!
« Reply #63 on: November 06, 2016, 07:45:18 am »
@batchman: Yes. I've just tried it and it worked perfectly fine.
i dont think so, downloaded 14gb torrent, and through few days of seeding i got these stats on it
Code: [Select]
14.2 GB	415 GB	952 GB	0.436 29.3x
... dont think it was counted towards overall data, still messed up torrent stats pretty badly

i would propose whitelisting version 2.48 as the change was reverted and removing 2.47 (probably even blacklisting it?)

Sorry but you are not allowed to view spoiler contents.

I believe the update that caused the problem you've described was made in v2.45 of Tixati:

Code: [Select]
trackers now report all-time upload/download statistics (same as seen in transfer details tab) instead of re-zeroing on every run

Offline sneaker2

  • Member
  • Posts: 239
Re: Report *new* whitelisted client versions | Read the first post!
« Reply #64 on: November 06, 2016, 09:05:00 am »
Yes, they have been talking about it on their forum: https://forum.tixati.com/support/2932/
It seems some trackers can handle both reporting variations fine but bakabt isn't one of them. The official torrent specs aren't unambiguous as to whether or not this reporting style is correct.

Offline SideChain

  • Member
  • Posts: 4
Re: Report *new* whitelisted client versions | Read the first post!
« Reply #65 on: November 09, 2016, 12:54:50 pm »
Just read through it. RIP the guy on a private tracker that has hundreds of GB reported by Tixati.

Offline mehdus

  • Member
  • Posts: 1
Tixati 2.49
« Reply #66 on: December 08, 2016, 04:28:08 pm »
Tixati 2.49
Quote
Tixati version 2.49 is now available. This update includes several important fixes and improvements:
fixed problems with Linux kernel 4.8.10 and newer causing unexpected socket closure
new setting for maximum simultaneous DHT searches
default maximum simultaneous DHT searches raised to 20 (from 12)
several minor compatibility updates and fixes to the internal URI parser
added new scheduler action that exports configuration file backups
added new scheduler action that randomizes incoming port
several minor internal framework updates to leverage newest C++17 features
added new GUI box classes to support better layout positioning methods
minor updates to GUI buttons, checkboxes, and radio boxes in preparation for new platforms
improvements to internal QoS prioritization for outgoing UDP message queues
several optimizations in transfer piece handling and hash-checking routines to save CPU time
redesign of DHT query processor soft-throttle system for much smoother engagement under high load
updated IP-location tables

Offline Blarghie

  • Member
  • Posts: 4
    • Lewd File Hosting
Re: Report *new* whitelisted client versions | Read the first post!
« Reply #67 on: December 14, 2016, 07:41:58 am »
qBittorrent v3.3.8
Quote
    FEATURE: Start using new libtorrent 1.1.x APIs (needs at least 1.1.2). Still unofficial support. (glassez, sledgehammer999)
    FEATURE: Add a new DHT bootstrap node run by libtorrent author arvidn. (sledgehammer999)
    FEATURE: Option to disable tracker's favicon download. (sledgehammer999)
    FEATURE: Shift + scroll = horizontal scroll. Closes #5980. Only for TransferListWidget, PeerListWidget. (Chocobo1)
    BUGFIX: Actually set new path as default when checkBox is enabled in Add New Torrent dialog. (erikssm)
    BUGFIX: Properly fix the handling of default save path store/load. (sledgehammer999)
    BUGFIX: Fix crash when restoring from tray. Closes #5854. (Chocobo1)
    BUGFIX: Export torrents added only after the setting was enabled. (sledgehammer999)
    BUGFIX: Delete old rss favicon before assigning new one. (sledgehammer999)
    BUGFIX: Don't revert save path value in the Dialog when metadata are received. Closes #5482. (sledgehammer999)
    BUGFIX: Don't ever stop seeding forced torrents. Closes #5784. (sledgehammer999)
    BUGFIX: Fix potential crash in TransferList widget. Closes #5873. (Chocobo1)
    BUGFIX: Sort torrent names case insensitively. (Yez Ezey)
    BUGFIX: Fix mistake in getting values for sorting in TransferList widget. (Anton Lashkov)
    BUGFIX: Fix memory leaks. (dzmat, Chocobo1)
    WEBUI: Fix webui port overflow. (thalieht)
    WEBUI: Changed meaning of the value of the 'dl_limit', 'up_limit', 'alt_dl_limit' and 'alt_up_limit' tokens. The value is expressed in bytes and not in KiB. (sledgehammer999)
    WEBUI: Don't request client SSL certificate. Closes #3883. (borouhin)
    WEBUI: Bump API_VERSION and API_VERSION_MIN to 11.
    SEARCH: Fixed extratorrent search not working Closes #5736 #5753. (Yez Ezey)
    SEARCH: Update Demonoid plugin. (ngosang)
    SEARCH: Remove TorrentReactor plugin. (ngosang)
    SEARCH: Fix python auto install, deletion of installer and use 3.5.x series for Vista+. Closes #5871. (sledgehammer999)
    SEARCH: Set /usr/local/bin before default PATH on macOS. closes #5639 #5571. This enables finding newer python installs. (Yez Ezey)
    COSMETIC: Log: set embedded Tracker [OFF] msg type as info. (thalieht)
    COSMETIC: Remove (mostly) useless log warnings about tracker's favicon. (sledgehammer999)
    COSMETIC: Change RSS view layout to horizontal. Closes #5920. (Chocobo1)
    OSX: Fix crash on exit using Qt4. (Yez Ezey)
    OSX: Change QSettings to IniFormat on macOS. Closes #5770 #5808. (Yez Ezey)
    LINUX: Workaround a Qt5 bug which results in a flood of network interface change singals. (Eugene Shalygin)
    OTHER: Turkish translation for installer. (Burak Yavuz)
    OTHER: Update portugueseBR for installer. (DaRKSoM)
    OTHER: Update portuguese for installer. (EdwardLinux)
    OTHER: Add --disable-qt-dbus to configure if $host_os is macOS. (Yez Ezey)
    OTHER: New translations: Icelandic, Latvian, Malay, Occitan, Uzbek.
    OTHER: A whole lot of code refactoring by various people.

qBittorrent v3.3.9
Quote
    BUGFIX: Fix slider for per torrent speed limits when no global speed limit has been set. Closes #6046. (sledgehammer999)
    BUGFIX: Fix GUI for proxy settings. Closes #6045. (sledgehammer999)
    OSX: Correctly migrate settings/rss/usage stats in macOS. Closes #6041. (sledgehammer999)
« Last Edit: December 14, 2016, 09:19:11 pm by Blarghie »

Offline christantoan

  • Member
  • Posts: 10
Re: Report *new* whitelisted client versions | Read the first post!
« Reply #68 on: December 17, 2016, 08:55:27 pm »
qBittorrent v3.3.10
BUGFIX: Fix share ratio limiting. Broken by commit 259b5e51c49b744. Closes #6039 #6048. (sledgehammer999)[/font]
BUGFIX: Case insensitive sort for client column. Closes #6054. (Oke Atime)
BUGFIX: Make resume/pause menu items clickable. Closes #6040. (Oke Atime)
WINDOWS: Make the updater to look for the x64 installer if running x64 version. (sledgehammer999)[/font]

Sorry that I can't quote properly. When I try to quote and I press preview, the whole formatting changes (the quote parantheses are lost and changed into somethings like
Code: [Select]
[size=12px][color=rgb(40, 47, 51)]...[/color][/size][/font]
etc)
« Last Edit: December 18, 2016, 09:46:29 pm by christantoan »

Offline Feldmarshall

  • Member
  • Posts: 2
Re: Report *new* whitelisted client versions | Read the first post!
« Reply #69 on: December 22, 2016, 11:59:44 am »
Tixati v2.51

Quote
Tixati version 2.51 is now available. This release contains several very important bug-fixes:

    fixed multiple problems with tracker connection header formatting
    sequencing of config file saving and overwriting is now handling orphaned temp files properly
    sequencing of config file saving and overwriting is now handling orphaned temp files properly
    fixed problems overwriting temp config files during load error recovery
    download completion commands should now work correctly
    minor issues with peer selection have been fixed
    numerous other minor problems throughout the program due to an issue with a recent build-chain upgrade have been fixed

Offline Dready777

  • Member
  • Posts: 1
Re: Report *new* whitelisted client versions | Read the first post!
« Reply #70 on: February 24, 2017, 04:57:11 pm »
Tixati v2.53

Quote
Version 2.53 is now available. This is a major upgrade with several important fixes and improvements.

All channels now have a fully decentralized forum that is available next to the Chat tab. Messages are organized into a threaded view, numerous layout options are available, and a full set of moderation controls allow the channel's operators to maintain their forum. Private messages between users can also be posted and are encrypted against the recipient's public key.

Other aspects of channel operation have been greatly improved as well. Shared user data, such as links, text, and forum messages, are now automatically segmented with a much more intelligent algorithm, which minimizes the bandwidth used to propagate changes when a small amount of content is added to a large shared collection. We have also spent a lot of time and effort working on the channel connection to connection protocol so that synchronization of user data is much more reliable and efficient.

There have also been numerous improvements throughout the core framework that underpins the entire program. We have made several fixes and improvements to our cross-platform native GUI toolkit, and have also made performance-critical optimizations in some of the core string-processing and encoding routines that are relied upon throughout the app.

Offline christantoan

  • Member
  • Posts: 10
Re: Report *new* whitelisted client versions | Read the first post!
« Reply #71 on: March 04, 2017, 07:05:46 am »
qBittorrent 3.3.11 (long changelog)
Sorry but you are not allowed to view spoiler contents.

Offline overmind

  • Member
  • Posts: 76
Re: Report *new* whitelisted client versions | Read the first post!
« Reply #72 on: March 09, 2017, 08:16:59 pm »
Also regarding to qbittorrent

Tuesday March 7th 2017 - NOTICE to tracker operators: User agent change https://www.qbittorrent.org/news.php

Quote
Starting from the next version (v3.3.12) qBittorrent will use the following user-agent format:

qBittorrent/A.B.C.DE

A, B, C and D are numbers indicating VERSION_MAJOR, VERSION_MINOR, VERSION_BUGFIX and VERSION_BUILD respectively.
If D is zero it will be omitted. The 3rd dot(.) will be omitted in this case.
A, B and C will always be present.
E is a string and possible values of it are alpha, beta and rc. They might not appear in all lowercase. Also they might appear numbered eg alpha2.
If E is empty it will be omitted. This indicates a stable release.
There is no connection between D and E. One might be present even if the other isn't. To sum up and give an example, the user agent that v3.3.12 will use is qBittorrent/3.3.12.
Quote
The change however affects only user-agent sent with HTTP requests - the peer ID remains the same.
« Last Edit: March 11, 2017, 10:01:08 pm by overmind »