Profil adatok

További bemutatók

Egyéb

Legfrissebb hírek

Tracker Traffic - 17.08.25

[ This is going to be a tad technical. ]

While you have been ripping, tagging and seeding, we have been grappling with infrastructure challenges of the sort that arise in heavy traffic. We know our users — good-looking and intellectually curious as you are — enjoy an occasional peek under the hood. That is the goal of today's post: a glimpse into the technical aspects of tracker management.

As per this external tally, we have the privilege to connect a lot of peers. To contextualize that spreadsheet, our peer count exceeds the next largest (MAM) by ~50% and the next most frequented music tracker (OPS) by ~3x. In the words of poet Kendrick Lamar, they not like us.

StarLord wrote:Because our torrents have a smaller size, our announces arrive in bursts; with growth, these bursts compound. We track more torrents, more peers, more snatches, more announces.What does this mean in practice? Well, in a recent one-hour window, ocelot processed 37,156,462 requests originating from 20,432 different IPs on behalf of 23,776 users. Traffic patterns vary but this is reasonably representative, if a touch high. More than ½ of all announces arrive via HTTP/1.1, roughly ⅓ via HTTP/2 and just a few via HTTP/3 or HTTP/1.0 (yes, really 1.0). In a proximate one-hour window, ~123GiB of data traveled on the wire between your torrent clients and the tracker. This amount includes not just application-level data (more on that below), but also TCP overhead and the TLS handshake:

Source: Cloudflare

How does that handshake look vis-à-vis RED?

That is 3,694 bytes of just TLS + TCP overhead, i.e. the bandwidth cost of initiating then closing a secure connection. For comparison, at the application layer during a typical announce, the client might send 362 bytes to receive a 392 byte response from the tracker, incurring some additional TCP overhead along the way. In other words, for BitTorrent, the data transfer for simply "speaking" TLS far exceeds the application payload. To avoid over-paying this toll on announces occurring in bursts, clients ought to send multiple requests over a single connection, utilize multiplexing and/or TLS session resumption.

Currently, five clients make the bulk of all requests; remarkably, just one (Transmission) tends to reuse connections! In the case of popular clients Deluge and qBittorrent, both of which announce via libtorrent-rasterbar, there is no reuse at all. It appears this problem was acknowledged by the developer in 2020 but unfortunately not prioritized. rTorrent uses a separate libtorrent library under the hood and appears to send announces via libcurl.

In the table below, the small percentage of connection reuse associated with qBittorrent reflects a custom reverse proxy. If you are interested in configuring that to conserve bandwidth (both ours and yours), please get in touch. Better still, if someone could convince the developers of libtorrent-rasterbar to adopt modern protocols and best practices.

What are the most common (top five) torrent clients?

   client    |     IPs    |     users    |    requests    |  app_traffic  | connection_reuse

-------------+------------+--------------+----------------+---------------+---------------------------

qbittorrent  |      11294 |        10792 |       14891274 |     10.70 GiB | 874020/14891274 (5.87%)  

rtorrent     |       3587 |         6909 |       11272780 |      5.77 GiB | 1814458/11272780 (16.10%)

transmission |       4213 |         4185 |        8110603 |      4.08 GiB | 7384086/8110603 (91.04%)

deluge       |       2342 |         2656 |        1599822 |      1.17 GiB | 0/1599822 (0.00%)        

utorrent     |       1028 |          894 |         934025 |    719.48 MiB | 960/934025 (0.10%)

[ this and all other data based on same one-hour window ]

Some of you are still announcing in plaintext ...

tls_protocol |   requests   |

-------------+---------------

TLSv1.3      |    32663134  |

Plaintext    |     2368765  |

TLSv1.2      |     2124563  |

Which client versions are most common?

+-------------------------------------------+-------+------------+--------------+

| Client_Version                            | Users | % of Total | Multi-Client |

+-------------------------------------------+-------+------------+--------------+

| rtorrent/0.9.8                            |  5088 |       21.8 |          763 |

| qBittorrent/5.1.0                         |  2299 |        9.9 |          305 |

| qBittorrent/5.1.2                         |  1795 |        7.7 |          256 |

| Transmission/4.0.5                        |  1498 |        6.4 |          291 |

| rtorrent/0.9.6                            |  1336 |        5.7 |          206 |

| Deluge/2.1.1                              |   950 |        4.1 |          285 |

| Transmission/3.00                         |   944 |        4.1 |          241 |

| Transmission/4.0.6                        |   867 |        3.7 |          147 |

| qBittorrent/5.0.1                         |   835 |        3.6 |          155 |

| Deluge/2.2.0                              |   813 |        3.5 |          203 |

+-------------------------------------------+-------+------------+--------------+

[ Multi-Client = number of users using that client that also use at least one other ]

Largest seeders?

+---------------------------------------+--------+

| User                                  |    TiB |

+---------------------------------------+--------+

| https://redacted.sh/user.php?id=32427 | 331.87 |

| https://redacted.sh/user.php?id=00000 | 161.53 |

| https://redacted.sh/user.php?id=1738  |  70.35 |

| https://redacted.sh/user.php?id=27212 |  62.64 |

| https://redacted.sh/user.php?id=00000 |  39.37 |

| https://redacted.sh/user.php?id=4204  |  32.26 |

| https://redacted.sh/user.php?id=31077 |  31.73 |

| https://redacted.sh/user.php?id=00000 |  31.26 |

| https://redacted.sh/user.php?id=00000 |  28.71 |

| https://redacted.sh/user.php?id=38673 |  28.09 |

| https://redacted.sh/user.php?id=00000 |  27.30 |

| https://redacted.sh/user.php?id=53567 |  27.19 |

| https://redacted.sh/user.php?id=00000 |  27.18 |

| https://redacted.sh/user.php?id=54778 |  25.59 |

| https://redacted.sh/user.php?id=00000 |  22.40 |

| https://redacted.sh/user.php?id=33185 |  21.64 |

| https://redacted.sh/user.php?id=00000 |  20.92 |

| https://redacted.sh/user.php?id=00000 |  20.18 |

| https://redacted.sh/user.php?id=59792 |  18.98 |

| https://redacted.sh/user.php?id=5169  |  18.73 |

+---------------------------------------+--------+

These numbers are impressive but potentially misleading. Underlying data does not determine announce (and thus, traffic) patterns; rather, it is the number of seeds. In the latter context, there is incomplete overlap with the above list of largest (data) seeders.

+---------------------------------------+---------+

| User                                  |   Value |

+---------------------------------------+---------+

| https://redacted.sh/user.php?id=32427 | 862,697 |

| https://redacted.sh/user.php?id=00000 | 359,534 |

| https://redacted.sh/user.php?id=1738  | 289,518 |

| https://redacted.sh/user.php?id=00000 | 138,782 |

| https://redacted.sh/user.php?id=53567 | 107,345 |

| https://redacted.sh/user.php?id=27212 |  89,112 |

| https://redacted.sh/user.php?id=00000 |  81,649 |

| https://redacted.sh/user.php?id=00000 |  70,602 |

| https://redacted.sh/user.php?id=31077 |  66,266 |

| https://redacted.sh/user.php?id=112   |  64,234 |

| https://redacted.sh/user.php?id=00000 |  62,268 |

| https://redacted.sh/user.php?id=00000 |  62,202 |

| https://redacted.sh/user.php?id=5169  |  58,725 |

| https://redacted.sh/user.php?id=00000 |  56,262 |

| https://redacted.sh/user.php?id=00000 |  52,880 |

| https://redacted.sh/user.php?id=00000 |  52,694 |

| https://redacted.sh/user.php?id=33185 |  52,679 |

| https://redacted.sh/user.php?id=00000 |  47,624 |

| https://redacted.sh/user.php?id=4204  |  47,283 |

| https://redacted.sh/user.php?id=64486 |  45,204 |

+---------------------------------------+---------+

[ 00000 UIDs correspond to users who declined attribution ]

The user (Complex) seeding 862,697 torrents generates less traffic with the tracker than those seeding much less. Complex uses qBittorrent, routing via Caddy's reverse proxy, which converts HTTP/1.1 → HTTP/2 and pushes thousands of announces over a single connection. The second largest seeder uses Transmission, which fortunately reuses connections out of the box.

What's the bottom line?

Security is paramount: HTTPS trumps HTTP. We have previously indicated that RED will not forever support plaintext. Given the nature and amount of traffic we receive, TLS skews up the overhead:payload ratio. Connection reuse, multiplexing and generally modern techniques push that ratio down. Security, performance and efficiency are not mutually exclusive; we can pursue them all.

Discuss this post here

Best Releases of 2024: Final Results & Spread the Love 2025 - 17.02.25

Good things come in pairs, and this announcement is no different. Not only are we announcing the very best albums to check out from 2024, but be sure to keep reading below the fold for the commencement of our eighth annual Spread the Love charity event, which is accepting entries as of right now!

We also are thrilled to welcome our newest member to our Staff team — the lovely CocaCola — so please say hello when you see them on IRC or while browsing the site.

We're also extending our heartfelt thanks and appreciation to Eclipse, who has recently stepped down after four incredible years of serving all areas of the site, including managing our interview system and leading our amazing Interview Team.

The results are in!!! Redacted chose the best releases of 2024 and once again pop reigns supreme. While it may have been a Brat 2024, Redacted once again displayed a vast appreciation of different genres and artistic styles. So what did Redacted vote as the best releases of 2024? Explore the lists, analytics, and collages below to find out!

More people participated this year than ever before, with a record 636 of you posting a list. Compared to last year, fewer overall releases got suggested, but there was still a grand total of 3407 unique releases in our lists. And like last year, everyone who posted has received a badge for participating! As always, thanks so much for contributing your list.

So what are the best albums of 2024? Check out the collage below to see:

Redacted's Official Top 100 Albums of 2024!

The Top 15 Albums of 2024

Note: the torrents listed in this announcement are not freeleech or freeload.

Other collages highlighting various stats can be seen here, with further breakdowns being in the stats post following this one. You can view cover grids of your lists in the stats post as well!

Thanks to all our uploaders! Over 251 members uploaded music that made the top 100. Our top uploaders were rodriguito, ilikepeaches, SadPeterPan, hubyfaterk3, Perun, Amethyst63, and sharky. These seven users each uploaded over 10 of the top 100 list submissions, and in total contributed 181 releases. Check out the full list of all 251 uploaders in the stats post!

Big thanks to the members developing excellent scripts to automate the results, and to dubiasu, sharky, hypermodified, & tentaculaire for helping with the collages, post, and graphics. And a big thanks again to Saturn for adding the new badges to the site.

Let's get the discussion started! Use this thread to let us know why you thought your list was best, what you think is missing, and any gems you happen to find in other users' lists.

Previous end of year threads and collages:

2016 Thread | 2016 Results | 2016 Collages

2017 Thread | 2017 Results | 2017 Collages

2018 Thread | 2018 Results | 2018 Collages

2019 Thread | 2019 Results | 2019 Collages

2020 Thread | 2020 Results | 2020 Collages

2021 Thread | 2021 Results | 2021 Collages

2022 Thread | 2022 Results | 2022 Collages

2023 Thread | 2023 Results | 2023 Collages

2024 Thread | 2024 Results | 2024 Collages

A big thanks to Takaji for the tastefully krafted artwork!

Happy Valentine's Day from Redacted, and welcome to our eighth annual Spread the Love charity event! This year, we're bringing this wonderful tradition into a new quarter century, in honor of the unparalleled Carl. We encourage you all to Spread the Love this year with a donation of food, clothing, or household items* to your favorite local charity. Although this is a contest with prizes on offer, any reward we distribute cannot match the importance of helping the less fortunate. To participate, simply post a picture in the Contest Entry Thread of what you are honestly donating with your username clearly visible. Optional: Please feel free to describe the charity you chose, and why. At the end of this drive, we will randomly draw five users to earn prizes such as:

• Custom title
• Contest winner badge
• 25 FL tokens
• Eternal gratitude

One entry post per person, but you may share multiple donations in that one post. The drive will run for one month, until midnight UTC on March 15. We look forward to seeing you all Spread the Love outside Redacted once again.

* Cash donations are welcomed by many charities but are not a part of this contest.

Please use the Spread the Love contest entry thread to submit photos, and the discussion thread for any commentary and chitchat regarding the contest.

News - 12.03.22

The site is currently down for maintenance.

News - 23.11.21

Half a Decade

Five years ago, a star site was born. The circumstances were far from ideal: our initial community of refugees was still reeling from loss. We owe much to our precedessors, and shall never forget the site we wistfully recall as a mirage. The path from then to now was turbulent, and we have learned some lessons along the way. Chief among them is that our users, and their varied contributions, are at the core of our success. We are immeasurably proud of everything you — the uploaders, rippers, helpers, interviewers, seeders, reporters, editors, the list goes on — have built. This is not a curtain call, but you nevertheless deserve a standing ovation for your achievement, and the central role you have played in helping us reach this milestone.

As the old adage goes, time flies, and nothing lasts forever. We must enjoy the ride, but also hold one another to account. To that end, we hear the voices of constructive criticism. Many who challenge certain aspects of the site's philosophy and decisions, are among its most ardent supporters and contributors. That is a sign that you love this place like we do, and want it to evolve for the better. While we cannot always deliver what you want, we promise to consider your suggestions with the nuance they deserve, and be more diligent in providing context for our decisions.

Of course, no birthday party is complete without party favors, which are detailed below. Enjoy!

Everyone should now have 50 FL tokens to grab whatever you would like! The tokens will expire on January 7, 2022 at 23:59 UTC. If you don't use them, you will lose them. To receive tokens your account must have existed and been leech-enabled at the time of this announcement. You may consult Freeleech Tokens to understand how these work.

The following torrents, comprised of user recommendations, have been set to Freeload until November 30 23:59 UTC, which is a new feature designed to reward long-term seeding and retention. When a torrent is marked Freeload, only current seeders and those who have seeded in the prior week, accrue upload credit for data they send to the swarm. No one is charged for downloading.

News - 01.10.21

Potential issues accessing the tracker, IRC network or site via SSL

Public Service Announcement

Accessing the tracker, IRC network or site via SSL.

TL;DR

On September 30 2021, an old root certificate of our SSL Certificate Authority expired. Technical details are available at the end of this post, but this was not a surprise, and had been telegraphed for quite some time. This is not a site or tracker bug. Most of our users, operating modern browsers and devices, should not notice any change. However, those on older desktops or servers, may have trouble connecting to our HTTPS tracker (HTTP is unaffected), SSL IRC server or site, and therefore have to update some software, or manually download a certificate.

How do I know if I am affected?

If, in the past 48 hours, you encountered errors such as 'Peer certificate cannot be authenticated with given CA certificates', 'unspecified system error', or complaints from an application that our SSL certificate has expired (it did not), you are likely impacted. Note that Firefox maintains its own root certificate store, so while your browser may be fine, other applications, such as your torrent client, may still not function with RED via SSL.

Hang on a minute, why are none of my other trackers impacted?

Perhaps they are using a different Certificate Authority; the issue described in this post only affects Let's Encrypt.

What should I do?

If this is happening on a managed seedbox, reach out to your provider, and let them know they need to update your SSL software / configuration. You can guide them by noting this issue is caused by the recent expiry of the Let's Encrypt's DST Root CA X3 certificate.

If this is happening on your own desktop or server, the solution depends on your OS and other details. First, see if you can fix the issue yourself by following the links below. If that fails, do not hesitate to ask for Help. As a last resort, temporary solution for tracker-related issues, you can remove the s from https in your announce URL.

Useful Links

https://letsencrypt.org/docs/dst-roo...eptember-2021/

https://letsencrypt.org/docs/certificate-compatibility/

https://docs.certifytheweb.com/docs/...9-letsencrypt/

https://community.letsencrypt.org/t/...ersions/141550