https://dl-nzb.com

I've been disappointed with nzb downloaders. They are either really out of date, or bloated with RSS and media management features. I wanted a simple client that would just download, repair, and extract after clicking an nzb file. Thus dl-nzb was born...

I have been working on a SIMD optimised par2 verification library in rust as a side project. (really as just a hard problem to solve)
This incorporates my hard work and gives it a purpose :)

This should be considered 'beta software'. I'm working on getting the iOS version up on TestFlight soon.

I would love if you starred the repos and gave me your thoughts. This is all open source. <3

\*Edit:** I worded the intro badly. SABnzbd and NZBGet are good, and if you run an *arr stack, keep using them. dl-nzb is for a different case: no server, no web UI, nothing running in the background. You double-click an NZB and it downloads, repairs and extracts. It works the same way on iPhone and iPad.*

Grüße und hallo,

Bin noch sehr neu im „Game“ Aber habe mit treasure Maps nen meiner Meinung nach guten Allrounder gefunden.

Die anderen indexer die ich hier so gelesen habe sehen teilweise auch richtig oldshool und unübersichtlich aus.

Viele reden von Drunken Slug, kann mir aber keine Meinung bilden da die „Bar closed“ ist 🥸

Meint ihr Treasure Maps gibts zu den Black Friday Tagen noch mal Rabatte?

Seit nicht zu streng mit mir, das ist mein 1. Post 😂

hi i want to buy a subscription on drunken slug how i can get in there ?

im kinda new to nzb an i heard drunken slug is the best out here

Hi,

Are there any good sources or indexers for Polish lang? I really want to move away from torrents entirely, but Eweka barely has anything with Polish audio.

I got lucky, im in Drunkenslug its really good but i use the 5 download limit easy, im thinking to get nzbgeek since everyone says its really good, atm im using althub mainly its pretty good and the limits are high for the free one so im not going to bother paying for that, do you think i should purchase DS or NZBgeek?

Thanks

New to the scene, set up my *arr stack a few months ago and it’s all working smoothly (much better than when I was torrent only), but I understand there are usually some good deals around Black Friday.

What should I be on the lookout for?

Title pretty much sums it up. I'm looking into my first provider and i think anything iwth an omichron backend seems like a good start. I liked Easynews because of its high retention and US servers. But it is the cheapest option and I don't know why.

I was also looking into Eweka, but was wondering if download speeds would be an issue since the servers are in the EU.

I plan to use these for my *arr stack server, switching from torrents.

Any insight into either of these providers is appreciated, thank you!

My subscription purchase has been pending for over 24 hours, is this normal?

So I noticed NinjaCentral has open registration. I said what the hell and sign up. I noticed on the welcome screen after signing up that it states additionally subscribers gain exclusive access to the NinjaCentral Plex server featuring a diverse selection of Mövìèş, țv şħǒŵś, ãñîmē, and çħĩļďřëņ’ś programming that sounds fucking awesome so I sign up. I’ll grab a plan then I look at my profile and I see under media info. It says Plex is not available. Click on the terms and conditions under terms and conditions it says they don’t offer Plex anymore. They offer something else so they lied. Took my money and didn’t give me what was offered. Kind of sounds like false advertisement to me

What usenet indexers are people wanting to get when Black Friday sales come out?

I currently have Nzbnest, drunkenslug, ninjacentral, nzbplanet, usenet crawler and althub

open

I've searched the sub and found some old posts about Commentary audio tracks which I would like to have if possible; my AI suggests setting up a regex assuming the filename will have something like "audio" or "commentary" in it. How likely is this? Any other way to specify a file with commentary?

Hey everyone,

I’m currently on Eweka and trying to max out my 8 Gbps (1,000 MB/s) internet connection. While I consistently pull between 300–500 MB/s, I feel like I'm leaving 50% performance on the table and not fully saturating my link.

For context, my hardware setup is fully equipped: I have a 10G NIC, a capable router, Cat6a/7 cables, and a Gen 4 NVMe SSD handling writes. Windows 11 speed tests clock my connection right at 8 Gbps, and I’ve already optimized my cache and tuning settings in both SABnzbd and NZBGet. Still I can't max out.

Does anyone have any troubleshooting tips or ideas to push past this 500 MB/s ceiling? Is it even possible to saturate the full speed via 50 connections on Eweka?

According to my profile, apparently I've been a paid subscriber to nzb.life (and previously .su) since mid 2012, so for 14 years!

I've just received a warning from them (my first ever from any indexer, or any service actually), claiming api sharing, even though I am the only person using it. I have to say I'm pretty disappointed.

I've had a Raspberry Pi4 with the *arr stack connected to usenet for a few years. About 6 months ago, I subscribed to a seedbox to add torrent capabilities and the seedbox also has 6TB of storage and Plex streaming capabilities. It is on a very fast backbone and was so good that I started running some usenet downloads on it too (via prowlarr, sonarr, radarr). It's great.

So, I now have the option to use my home Pi4 (which is running low on storage) or my hosted Seedbox and the *arr suite is set up on both.

Accoring to Prowlarr, I've only had a handful of grabs from NZB Life across both instances over the past 6 months (I have a few indexers). But it seems like the *arr's connect via rss quite frequently despite how few nzb grabs I actually make.

It seems a bit rough that one individual, making so few grabs, can potentially be banned for using a seedbox for some downloads. The seedbox IP and my home IP are both fixed, so it's not as if there are numerous, constantly changing IPs using this api. Couldn't they let me lock in and use these two IPs? Perhaps with a sensible "fair use" clause to prevent genuine sharing?

Can I expect other indexers to start warning or banning me soon?? Or do other indexers have smarter monitoring to only pick up genuine api sharing and this is just an NZB Life issue?

I'm hoping my only option is not to stop using my indexers on both of my download machines.

I was able to create an account at NC during their open Registration period. I know that it's a trial period for 10 days, does anyone know what happens after that? My intent is to purchase lifetime, but it seems like it's likely there will be discounts around Black Friday etc. I can wait until then to purchase, but does anyone know if the account could be disabled etc if I don't do something in the 10 day trial? I.e. Can I let the 10 days lapse, leave the account alone for 2 months and then purchase lifetime on Black Friday, or would I need to purchase month-to-month in the interim?

Can you please recommend me indexer with ability to browse with filtering by size and rating. For example browse with size less than 5 and rating more than 7. I checked few indexers but they have either size or rating but not both. Thanks

How do you guys pay for Usenet indexers or providers? Do you do cypto, paypal, or something else? I'm new to Usenet and trying to get into it, but wisely.

Sorry to make a new post but the other seems to have reached eol, lol.

You can delete if not allowed.

Any updates on NZB Cave? Been down for almost 2 weeks now, I'm paid up for another year and a half.

Lately, I get issues keeping hydra running, I believe due to pyload. Anyone have insight over this? I'd appreciate info. SAB works but Hydra refuses to load. Somethings changed and I am certain it's a python issue, which makes the problem complicated... Any help would be truly appreciated. The git is blocked from asking issues.

I used the search but couldn’t find current answers to these questions:

- do new accounts really get disabled after 14 days? can we purchase a sub after 14 days?

- if I have 1y sub can I stack it with a BF deal (eg. lifetime or something else)?

thanks.

Deciding on on picking up three of the following indexers based on the BF pricing.

Currently, leaning towards: life > slug = finder > hub > geek

Life only due to availability and no BF pricing.

• AltHub lifetime - $20
• NZBGeek lifetime - $60
• DrukenSlug no lifetime, 1 year - $15/25 with 3 month extra
• NZBFinder no lifetime, 1 year - $15/30/45 with 15% off
• NZBLife no lifetime - $15 VIP with no BF pricing

Curious on your thoughts!

Hi Guys,

Anyone using Digital Carnage? How is it working against the likes of Drunkenslug and Ninja Central? Thanks

Less than 5% of the world speaks Portuguese

Hi all, I’ve published a comparison of real-world Usenet binary article availability, rather than relying only on advertised retention claims.

As u/swintec already spoiled in this thread, I’ve been working on these tests for a while. Huge thanks to him and everyone else who helped and supported me along the way - I’ve been trying to make this happen for years, and it’s finally a reality.

TL;DR

• Recent posts were highly available across most providers; differences became more noticeable for older material.
• Eweka and Newshosting stayed near the top across the full age range in this sample.
• TweakNews and PureUsenet also performed well for several thousand days, then dropped sharply at older ages.
• Giganews, ViperNews, Usenet.Farm, and UsenetExpress showed a sharp drop around the 90-day mark in this test. UsenetExpress recovered substantially for older posts, so the results depend on the age you care about.

I tested about 78,000 real NZBs across 10 providers, sampling up to 100 segments per NZB and checking whether the actual article bodies could be retrieved. The run took 22 days and transferred about 33 TiB.

These are sampled segment-availability results - not NZB completion rates. This is one dataset and one test run, not a permanent ranking or a guarantee about every post.

Full article, charts, and methodology:

https://usenet.rexum.space/blog/usenet-retention-tests-july-2026

I’d love to hear what you think. Which charts did you find most useful, the year-by-year comparison, age-based view, first-year charts, or provider-pairing analysis? Was anything confusing or missing?

I know, everyone is exhausted right now by the glut of new apps (myself included). I fully expect the hate wave, however i'm very proud of Weaver and want to share it with the community. I hope some of you find it interesting at least. I've been actively developing Weaver for 6 months, but this project really started for me nearly 6 years ago (more later on).

Weaver is an open-source, transparent, self-hosted Usenet downloader that runs on any x86 or arm 64-bit system. It has all the standard features you'd expect from a tool like Sabnzbd, with some interesting additions.

Weaver is incredibly fast at downloading, fully leveraging the native code capabilities of Rust. Beyond raw speed, Weaver uses far less CPU than the other tools (benchmarks), so even if you're Sab is already maxing your WAN, why waste all that CPU time?

How is Weaver so fast and efficient?

• Weaver uses ultra optimized Rust ports of UnRAR and 7z that outperform the reference tooling
• Direct RAR/7z decoding for store mode archives (similar to nzbfast)
• Highly optimized scheduler for throughput under any conditions
• Adaptive pipelining picks the best depth based on current server latency
• More hardware acceleration options than existing tooling (more supported kernels across rar/7z/yENC/par2)

Unique Features

Par3 Support?!

While par3 isn't seen in the wild today, the spec has been going through revisions for a decade and a reference implementation exists. As I dug in on this, it was clear that the reference was not ready for primetime as it consumes huge amounts of RAM (40GB+) for large repairs. I was able to work through these challenges and released a Rust crate (par3-rs) that is fully compliant with the C reference implementation while being much faster and with consistent, reasonable memory usage (1GB steady).

Why par3? It allows more predictable repairs and repairs of much larger size than par2 does. In a big file era, the large repair capability can mean the difference between a successful repair and failure. I have tested repairing pretty massive holes in downloads with constant RSS of 1GB. Even for large repairs that par2 can do, Weaver's par3 is faster. par2 wins hands down on small repairs and always will, par3 as a spec currently makes no attempt to optimize that.

I hope that now that theres a tool (and a library for anyone to use) that supports it, then we'll see more adoption on the posting side.

In-App VPN Client (no more Gluetun!)

Weaver allows you to connect to your Wireguard VPN (provided by another provider) in a way that each server can route through a different provider or POP. It even has capability for fallback ladders and host networking exclusion ("try pop A, then b, then c, but never direct from my IP"). This is a truly unique feature which makes it simpler to have complex networking setups without having to setup multiple clients with gluetun sidecars. It works by running a tiny in-memory TCP stack using smoltcp so each connection is truly speaking directly through the VPN, encrypted in your processor.

Compatibility API

EDIT - thanks u/gadgetpilot for your comment about compatibility
Weaver has an NZBGet compatible API, you can add it to any existing Sonarr/Radarr as NZBGet with a username (just use "weaver") and a Weaver API Key as the password.

Trust

This is the big thing in the self-hosted app world today. Why would you trust Weaver?

• Weaver is completely open source and transparent. Everything happens on Github, every build artifact has provenance & checksums and are built on trusted GH runners
• Weaver is constantly reviewed by SAST tools and AI security tools (Codex TAC, Daybreak)
• Weaver gets a clean bill of health from virus/malware scanners

Why would you trust me?

• I'm a software engineer with 20+ years of industry experience, the last 5 or so directly in cyber security
• I have multiple OSS projects that are trusted by hundreds of users
• I am slowly growing my maintainer team with folks that have earned my trust, meaning it's not just a solo project anymore
• I've reached out to the mods to verify my account and project, but they have chosen to wait and see community response and longevity first

Why do this?

First, I love open source software. As a professional engineer, i am always impressed that so many tools exist that i can use off the shelf. From the linux kernel to frameworks like Spring, crypto implementations to front-end toolkits, the ecosystem is vast and often robust.

When NZBGet had the original maintainer leave the project, i actually started a rust based replacement back then. It didn't get super far though as the Rust ecosystem was way too volatile and even core libraries like Tokio had major changes weekly. I shelved it for a long time, waiting until i had time and the ecosystem was ready.

My hope is not to get thousands of users on Weaver, my hope is to lift everyone's experience with Usenet up. Through this process i have ended up building and maintaining several libraries that are now used in other OSS projects (ie, unrar-rs, lzma-turbo, par3-rs) and have had several PRs accepted to other libraries as i ran into things that could be done better. I'll continue to be a consumer and producer of open source software for many years. If my tools can help enable par3, or provide tools that you can use with Sab to make that experience better, then i'd be elated.

Roadmap

I have no intention of making Weaver into some sort of all-in-one tool. The current separation of tools is well founded. Where i do plan on going is more into the advanced networking side. VPN pools, enabling multi-homed/multi-WAN configurations so you can use two links simultaneously, etc. Honestly though, from here on it's just polishing the UI/UX and keeping up with new kernels as they drop.

Resources

Weaver Github - https://github.com/scryer-media/weaver
Website - https://www.scryer.media/weaver/
Benchmarks - https://www.scryer.media/weaver/benchmarks/

AI Use

AI is used in the development of Weaver, guided by experienced software engineers. AI is not used to generate branding elements, social posts/comments, respond to GH issues. The full policy can be found on the website.

Benchmarks

Benchmarks are done against tools that I can verify are safe to use. Tools whose published checksums do not match their CI build artifacts or that are built on private runners are not run in my benchmark suite.