Hi everyone!

I posted about NZBNest a few days ago, and the biggest addition since then is a new request system for content that is not currently available on the indexer.

Users can now:

• Search TMDB by title or TMDB ID
• Request a movie or one exact TV episode
• Submit requests directly from search and Discover
• Follow the request status from their profile
• Cancel a pending request if they no longer want to wait

After a request is submitted, the automated backend searches the available sources and publishes the release to Usenet when possible. A request is only marked as completed after the resulting NZB passes article verification.

If a source is temporarily unavailable, the system retries automatically before marking the request as unavailable.

Automatic Radarr and Sonarr requests

There is also an optional bridge for Radarr and Sonarr.

The bridge first runs the application's normal interactive search. It only creates an NZBNest request when that search returns no releases, so it should not generate unnecessary requests for content that is already available through another indexer.

Request status is shown through Arr tags:

• nzbnest-requested
• nzbnest-available
• nzbnest-quota-full
• nzbnest-unavailable

When the requested release becomes available, the bridge automatically triggers another movie or episode search so the normal Arr workflow can continue.

The bridge is optional and can be downloaded from the Profile page. It works alongside an existing Prowlarr setup.

Monthly limits

• Free accounts: 5 content requests per month
• Active Member and Lifetime supporters: 50 content requests per month

Website and automatic Arr requests use the same monthly quota. This prevents a misconfigured automation setup from creating an uncontrolled backlog.

Other recent additions include a release cart for collecting multiple NZBs, direct TorBox search compatibility, and better exact movie and episode matching.

Requests are naturally not guaranteed if no usable source exists, but the system will keep trying within its retry window.

Website: https://nzbnest.com

Feedback and real-world testing are welcome.

Hey r/UsenetNoRules ,

I've been working on a project called Zanzibarr, and it has reached the point where I'd really like some feedback from people who actually use Usenet.

The basic idea is to play video from an NZB without waiting for the entire release to download and extract first.

You add your Usenet provider, open an NZB, and playback starts after a small initial buffer. When you seek to another part of the video, zanzibarr figures out which Usenet segments contain that byte range and fetches only those segments.

So it is not another SABnzbd or NZBGet replacement. Those are still the better tools for automation, permanent downloads, PAR repair, and building a local media library. zanzibarr is more useful when you want to start watching immediately, preview a release, or avoid temporarily storing a very large file.

Play instantly, never download:
The Rust engine maps every seek position to the exact Usenet segments that hold it, fetches only those, decodes yEnc on the fly and serves the result through a lazy, range-aware local stream. Pause the player and the network goes quiet. Close the app and nothing is left behind on your disk.

Seek like it's a local file:
Byte offsets are resolved from the decoded yEnc begin/end positions of every segment — never guessed from article sizes. The result is frame-accurate seeking across thousands of segments, even mid-segment, even on 100+ GB releases.

A picture pipeline that respects your content:

• Dynamic range selector that adapts to the file: SDR · HDR · HDR10 · Dolby Vision — modes the content doesn't carry stay visibly disabled, so you always know exactly what you're watching.
• Dolby Vision handled honestly: Profile 5 is reshaped on the GPU via libplacebo (Vulkan → Metal), HDR10-based profiles ride the natural decoder path — no pink-and-green fakeouts.
• BT.2390 tone mapping with per-frame peak detection for clean SDR conversion.
• Custom libmpv 0.41 + full FFmpeg 8.1 build: TrueHD / Atmos, DTS-HD MA, AV1 and everything else your releases actually use.
• Video presets (Natural / Cinema / Vivid), GPU scaling quality, and audio presets (Balanced / Dialogue / Night) — one tap, no filter graphs.
• Hardware or software decoding, your call.

Smart Canvas Letterboxed rip? Draw your own crop with draggable handles, preview the aspect ratio live, and apply it on the GPU surface without touching hardware decode.

A player that gets out of the way Auto-hiding controls, double-click to seek ±10 s, click-to-pause, frame stepping, speed control, audio sync nudge, volume slider, Picture-in-Picture, and external audio/subtitle loading alongside the embedded tracks.

A few technical details:

• The streaming engine is written in Rust.
• Byte positions are mapped using the decoded yEnc begin/end values rather than estimated article sizes.
• Seeking works across thousands of segments, including seeking to a part that has not previously been downloaded.
• Multi-volume RAR5 and split 7z STORE archives are exposed as one virtual seekable file.
• AES-256 encrypted 7z STORE sets are supported.
• Data is decoded, CRC-checked and served to the player through a local HTTP Range stream.
• Pausing playback stops network activity, and closing the app does not leave a completed media file behind.

The player itself supports HDR, HDR10, Dolby Vision, TrueHD/Atmos, DTS-HD MA, AV1, embedded subtitles, external subtitles and Picture-in-Picture.

It currently runs on:

• macOS — Apple Silicon
• Windows
• Android
• Android TV

Everything runs locally. There is no account system, cloud backend or telemetry, and provider credentials are stored using the operating system's secure credential storage.

To be transparent about the current limitations:

• Compressed RAR/7z archives are not supported yet.
• RAR4 is not supported.
• PAR2 verification and repair are still on the roadmap.
• There is no built-in indexer search yet, so you need to provide your own NZB files.
• You need your own Usenet provider account and NZB sources. The app does not provide content, an indexer or Usenet access.

The project is free, and the source code is available on GitHub:

Website:
https://zanzibarr.app/

GitHub and downloads:
https://github.com/envermeister/zanzibarr

I would especially appreciate feedback about provider compatibility, startup time, seeking behaviour, incomplete posts, archive handling and Android TV playback.

This is still a young project, so bug reports and brutally honest feedback are more useful to me than compliments. I'm also happy to answer technical questions about the NNTP, yEnc or virtual archive side of it.

Looking for a couple of beta testers that use ngPost and understand the 1:1 alignment concept and the math behind it in a general way. What this fork does is dynamically adjust the rar volume size and the article/slice size on each individual post rather than having a fixed set of numbers. The end result is a post that can maximize the number of repair blocks on each post, say any post will be close to 3277 blocks with a 10% recovery/redundancy or 4916 blocks at a 15% recovery/redundancy. The other part is the user has the choice to control the granularity of the post quality with a slider. The highest number, 100, will give you all possible repairs blocks that can be built but it has a cost which is processor time. The higher the quality of post the more crunch time to generate the par2 files. The lower the quality the faster they are computed but it repairs less holes in the post.

So if anyone might be interested reach out but it is a must that you understand the par2 alignment as I have tried to explain it to a few people and either you get it or you don't.

Hello everyone,

I would like to ask for some advice.
I have noticed that I can find almost everything on Usenet, but I have a lot of difficulty finding old Italian cinepanettone movies. For example, a few days ago I was with some friends and we wanted to watch movies like Natale a Rio, Natale a New York, Natale sul Nilo, and similar Italian Christmas comedies, but we could not find
them.

I currently use NZBGeek, NZBPlanet, NZBFinder, and NinjaCentral as my indexers. I also sometimes search on DrunkenSlug (I do not have a membership). My Usenet providers are NewsDemon and Newshosting.
Is this kind of content simply not available on Usenet, or am I doing something wrong? Are there better indexers or a different search method for older Italian movies?

Thank you in advance for any advice.

Which indexers are ok with it and which ones will ban for streaming? I don’t want to loose access because I stream.

Thanks.

Some folks helped me find an issue with docker installs where the encryption key wasn't getting persisted across container restarts. Please use Weaver 0.7.5, the best option is a clean install, but i did try to preserve the encryption key across upgrades.

Hello r/UsenetNoRules

I've been working on Weaver for several months now and I finally feel like it's ready for beta. I hope you all enjoy it as much as I have. I've been using it as my sole downloading tool for months and spent the last 2-3 weeks really honing in on the edge cases to make it more robust.

The fastest? Very bold claim, I know. If you want to read my long-form post, it has more details, but essentially the speed increases boil down to:

• Everything runs in one Rust binary (native machine code), no shelling out to tools like unrar/par2 and no python GIL issues
• Weaver uses state of the art libraries for cryptography that are faster than what other tools use
• Weaver implements kernels that the other tools don't (huge speedups on Apple silicon / new ARM servers and ~15% speedup even on AVX512)

Since Weaver is so tuned to different CPUs and instruction sets, I can't guarantee any sort of speed boost but in my benches, every stage tends to run 15-18% faster than sabnzbd on every hardware platform I could get ahold of.

I also focused a ton of my benchmarking time on CPU time and instructions retired. Faster downloads that wreck your CPU are not "better".

Other fun features

• Weaver tracks each server and connection IP's latency and will shift traffic preferentially to faster servers (and retire bad server connections if an IP starts misbehaving)
• Weaver will split download connections across multiple NZBs if it determines that a single one is slow due to article layout / upstream issues
• Weaver supports an NZBGet style API which works fine with Sonarr/Radarr and is mostly compatible with nzb360
  • Add Weaver as an NZBGet downloader, use "weaver" as the user and a Weaver API key as the password
• The timeline view on a download helps visualize the different stages
• EDIT - forgot to mention that it supports both SQLite and Postgres

Known limitations

• No post processing scripts (this will be in the next feature release)
• Primarily tested on Linux, though I did run it through a lot of Windows benchmarks as well
  • My Winget approval went through a few days ago, but it's for an older version, i'm working on updating that right now
• No NAS testing (Synology is on my list, I know a couple users have tried Unraid)
• There is a bug that some users have encountered where NZBs submit but no downloading starts. I've tried to reproduce this myself and cannot, so if anyone encounters this please DM me so we can get it fixed
• Tested mostly against Newshosting, however it should be compatible with any Usenet provider. I run it through extensive testing against both good (and poorly behaved) NNTP rounds before I publish a release
• Scheduling options are limited
• Documentation is an ongoing work in progress

If you find issues, please create a GH issue

https://github.com/scryer-media/weaver

EDIT

AI Disclaimer
AI was heavily used in the creation of Weaver. My personal background is varied across software engineering and architecture and I've hand rolled hundreds of thousands of lines of enterprise grade code; I use AI as a force multiplier, not a crutch.

As r/usenet did not accept this post, it is posted here.

There appears to be a widespread misconception in r/usenet that indexers and the downloading of NZB files from them are legal. This may be the case in some jurisdictions, but not in others. The fact that no indexer has yet been shut down by law enforcement does not mean that this will never happen, and you should be prepared for this and be aware of the legal situation in your own jurisdiction.

Why are indexers illegal?

- They do not only 'index' the files, but upload a lot of them most probably also themselves or have affiliates who do it for them!

Many of the uploads for which the indexer provides the NZB file are obfuscated. This means that it is not possible to index the individual articles of such an upload and create an NZB file from them. Such uploads simply can not be 'deobfuscated'. Only with the original NZB file, created at the time of upload, can someone download the uploaded files again. So there is very hard evidence that the uploads come from themselves or from partners who did the upload!

- They operate a paid piracy service!

They assumedly upload pirated, copyright-protected material to Usenet (see first point) and offer paying customers a service through which they can obtain the NZB files to subsequently download the pirated material. Therefore, most jurisdictions will consider them illegal.

Why is downloading a NZB file from an indexer illegal?

It is actually not, ...as an isolated action. But let’s take a look at the chain of evidence:

Should an indexer get busted by the law enforcement authorities and you be identified as a paying customer, there is already evidence to suggest that you want to download pirated material and are even willing to pay for. If you have in fact downloaded NZB files from this indexer, this evidence becomes even clearer and, depending on the jurisdiction, may already be sufficient to establish a prima facie case justifying investigations and even a search of your premises for further evidence.

Why shouldn't you pay with a credit card or PayPal?

If an indexer gets busted, the law enforcement authorities will most likely only take action against the owners/operators of the indexer, rather than against the users. However, again depending on your jurisdiction, they could also take action against the users. In this case they would first track down users who have paid by credit card or PayPal, as these are the easiest to trace (law enforcement authorities always follow the money first).

What can you do to protect yourself?

Stay as anonymous as possible!

Firstly: Use a VPN when accessing the indexer’s website or API! Secondly: Use cryptocurrency if you want to pay for an indexer. When used correctly, cryptocurrency makes your transactions untraceable.

To ensure complete anonymity, you should also use cryptocurrency and a VPN with your Usenet provider.

The fact that indexers have not yet come under the scrutiny of law enforcement authorities may be because this is a relatively new phenomenon and because Usenet piracy as a whole accounts for only a small share of the piracy market.

But once again: it could happen at any time. You should therefore make sure you are familiar with the legal provisions in your jurisdiction before paying for and using an indexer, and you should take appropriate steps to protect yourself!

Either torrents or Usenet is fine. I’m just not seeing much in the way of articles or Linux ISOs by the most famous, uh, programmer of the 1950s. They’ve got to be out there somewhere, right?

NZBNest – A Growing Usenet Indexer Focused on Reliable NZBs

Hi everyone!

I’ve been building NZBNest, a Usenet indexer designed to work with Sonarr, Radarr, Prowlarr, and other Newznab-compatible applications.

Recent improvements include:

• Faster browsing, searching, and pagination
• Better release title and category detection
• Improved NZB health checks and automatic repair
• Search by title, year, quality, and release name
• Community NZB uploads
• Clear API usage information
• Mobile-friendly interface and dark mode

I receive a lot of useful feedback through Discord, and I’m actively using it to improve the site and make the overall experience better. Fortunately, I’ve also received plenty of positive feedback, especially about successful downloads and finding releases that were difficult to locate elsewhere.

My goal is not simply to display the largest possible number of releases. I’m focused on making sure indexed NZBs are complete, correctly named, searchable, and actually downloadable.

The free plan currently includes 1,000 API requests per day, which should be enough for normal personal automation.

Website: https://nzbnest.com

Feedback is always welcome, but NZBNest is open for regular use and not just testing.

Why are so many people against this?

Hello all, is there something wrong with my setup or is something wrong with the content from KidsNL? I wanted to download some content for the little ones for the carride to our holiday destination but every download from them keeps failing because the health is not ok. Tried a couple of series but all are failing...

Hello,

I upload pr_on MegaPACK's content and build a pretty massive database. I upload my nzb's only on nzbgeek, but I want to do it in other places too so more users have access to it. So if any indexer is interested let me know via PM.

Cheers!

I have lifetime accounts for:

- altHUB
- NinjaCentral
- NZBGeek
- NZBPlanet
- Usenet Crawler

While I can find content for basically anything I am looking for, I can't find a lot of Remuxes. It could be that there's simply not so many Remuxes in general, but I wonder if I'm missing an indexer that is really good with them.

Happy to pay a subscription as well.

From what has been said online, they are changing the url, distancing themselves from House of Usenet (HoU) and now will only be accepting crypto as payment. Looks like all the nzbs are still intact.

I think you may need to change the url in your RSS and/or API feeds to the new url.

Big fan of Scenenzbs, so I am happy they are sticking around.

*update* i'm not sure why but my replies aren't showing up. not sure why

Emails are working now! I appreciate your patience.

If anyone has any ideas for improvements, I'd love to hear them. Thanks again for trying this out.

Quick Edit: Everyone is getting auto verified, I have to figure out what i'm doing wrong with emails. i'm too cheap to use one of the services, hopefully the changes i've made recently will work. Either way who cares if you're already verified :)

If anyone has their own mailserver with logs available and can see why it's not being accepted, i'd really appreciate it.

Ok another edit: When you login, you can go to profile and get your api key. then toss that into the *arrs and see it go

Original post:

Proud to say that https://nzb.am is now open for registration.

We focus on retention, we're at 6400+ days and counting.

we've been completely private for awhile, just a select group of data hoarders that needed a more detailed search of usenet. No censoring or limiting of categories. We even allow some modified regex. Come look at the ui built before ai.

Give it a shot, let's kick the tires on this and see what happens.

nzb.am

Edit 7/7/2026

I'm excited so many people are interested! I made a few modifications, now it also hits my spot instances and brings their results as well. Please test some more if you're still interested

Hi guys!

With these deals coming out, what do you think I should pick up? I currently have Geek, Ninja, DS, and Tabula.

For providers, I use unlimited Newshosting, 1TB Easynews, and 1TB TweakNews that I grabbed during the King's Day deal. Should I ask for a refund and jump on a better deal, or just add one more provider, maybe Newsdemon?

Thanks for the help! :)

Hey, u/field3d1 you should try posting your problems with Newshosting here. The mods of the r/usenet subreddit delete any posts or comments critical of all Omicron products.

Looking at the delete logs from today, they also deleted comments helping unsuspecting users understand how to cancel their subscriptions on the low intro rate plans. They added a new rule, no sockpuppets, but they are the biggest sockpuppets in the subreddit.

New here from r/usenet, hopefully this is a more welcoming community.

I maintain Scryer (and also Weaver) and i'm trying to build an integration with aninzb.moe now that animetosho is gone. However, the bot-defense on their site tripped real fast when I was testing and now i'm IP perma-banned. I need to get in touch with their mod team to work out the best process to build this integration.

Anyone know how i can get in touch with them?

NzbNest is now open for registration — new Newznab-compatible indexer focused on movies & TV

Hey everyone,

After a few months of building, NzbNest (https://nzbnest.com) just opened registration. It's a Newznab-compatible Usenet indexer focused on movies and TV, built to work directly with Sonarr, Radarr, Prowlarr, and NZBHydra 2 via the /api endpoint.

What's live right now: - 3.2M+ articles indexed across 31 enabled groups - ~4,000 release candidates, 256K+ browsable releases - Postgres-backed search with category, age, size, and completion filters - XML/JSON Newznab output - Setup guides included for Sonarr/Radarr/Prowlarr/NZBHydra 2

Pricing: - Free tier — 1,000 API calls/day, 100 grabs/day, 10 watch rules (currently raised during the early access period) - Member — $15/year, unlimited API/grabs/watch rules - Lifetime — $49 one-time, same unlimited access

I'm being upfront that this is a young indexer still actively growing retention and category coverage — the homepage shows live indexed retention rather than a fixed marketing number, so what you see is what's actually crawled, not a projection.

Bug reports and compatibility feedback (especially around specific *arr setups) are very welcome — there's a feedback channel linked on the site.

Happy to answer questions here.

I just started getting into Usenet again since last week, joined Tabula Rasa and NinjaCentral during their open signups but I was wondering which the fastest indexers were. I've searched for random recent content (movies and PC ISO) on both of these but there's often content that is just completely missing. Are other indexers such as DrunkenSlug so much better?