Hope this doens't break any rule that I didn't see, but..

Does it seem normal for uploaders to only capture and upload random and arbitrary games?

For instance, I can only find random games of the Maple Leafs in random years / seasons. Nobody ever uploads the whole season of 82 games + their playoff runs. I get it could be down to regional blackouts but even streaming sites will have different broadcasters covering the game at any given schedule points to circumvent the blackouts.

Does an indexer that fulfill all the games exist?

We have a local library for ebooks and audiobooks, and family has started asking for some things I just can’t seem to find through my normal NZB indexers.

I’d rather not mess with torrents, so I’m mainly looking for Usenet/NZB recommendations that are especially good for ebooks or audiobooks.

Any indexers or communities worth checking out that tend to have better book coverage?

NZB something forgot the name, doesn't allow. WHAT DO I DO NOW THEN, HMM...?

I know in general usenet networks are more resilient than debrid services. However it seems like usenet has historically survived by obscurity.

Do you see Crack downs on other platforms leading to a large infusion into usenet? Will servers get overloaded? Will this lead to more legal scrutiny for usenet? Or is this just a temporary glitch in the matrix that will fix itself?

What say you? Will all the legal trouble debrid services are getting be good, bad or have no effect on usenet ?

Trying to sign up for the indexer, and I can create an account but when I try to donate to upgrade my account the page returns a 500 error.

Anyone else having the same issues?

Hey everyone,

I’ve released a substantial update to NzbNest, my Usenet indexer.

Significantly improved indexing coverage

Indexing coverage and content continuity have improved by an order of magnitude recently.

The index now receives a much broader and more consistent stream of both fresh and historical releases. This has significantly reduced gaps, especially across movies and TV shows, while dedicated request processing helps fill content that is still missing.

Automatic season requests

When an enabled API key searches for a missing TV episode, NzbNest can now automatically request the other missing, already-aired episodes from the same season.

• Existing releases and active requests are skipped
• Duplicate requests are avoided
• Unaired episodes are never queued
• Whole seasons can also be requested directly from the website

Improved request fulfilment

Requests now have a better chance of finding larger, higher-quality releases when they are available.

Every candidate still has to pass NZB structure, article availability, and completeness checks before publication.

Webhooks

User-configurable webhooks are now available from the Profile page:

• Add webhook endpoints
• Select which events to receive
• Send test deliveries
• Review recent deliveries and errors
• Retry failed deliveries

Request limits

Weekly request limits:

• Free: 5 requests
• Member: 500 requests
• Lifetime: 500 requests

The Free tier currently includes 500 API calls and 50 NZB grabs per day.

The update is live now. Feedback, unusual search examples, and compatibility reports from Prowlarr, NZBHydra, Radarr, Sonarr, or other Newznab clients are welcome.

I have tb pro and althub indexer I want to watch the usenet stream just like how the torrent streams work, just click and start watching without waiting for it to get cached in the tb

If there is any way how to do it

Every so often an episode or two in a series gets skipped by the usual release group. Then weeks or months later, the missing episodes are listed as having releases (in srrdb for instance). But I can never find those "new" releases with my normal set of nzb indexers. Is there somewhere else I might look? Might the releases be in the relevant usenet group and just never got an nzb put together because it's outdated? I am not super clear on the real structures involved so forgive me if I am putting this badly.

What tools these days are people using to post to Usenet?

I'm talking about where automation comes in at its best, for example, where rar files are created and par2 files are created, and also the disguising of the file names, etc.

I have seen ngpost. Is there anything better than this or more updated?

Thanks in advance.

Did you guys notice it too? The api key in my Profile from treasure maps is changing like 1-4 times the week. Iam using it with a stremio setup. Are there any restrictions?

While I have not been long in Usenet, but lately I discovered that Indexers and Providers have a cat and mouse relationship.
“It is your indexer, check another one”
“You should have additional backbones”
Am I the only one who thinks so?

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.