r/UsenetNoRules

Good Usenet indexers for ebooks/audiobooks?

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?

reddit.com
u/MrD33ds13 — 3 days ago

Debrid legal trouble is it a bad sign for usenet?

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 ?

reddit.com
u/chris_socal — 4 days ago

SquareEyed donation Page broken

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?

reddit.com
u/jordanmlee — 5 days ago

NzbNest update: automatic season requests, improved fulfilment and webhooks

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.

reddit.com
u/redrick555 — 7 days ago
▲ 10 r/UsenetNoRules+1 crossposts

Does anyone else have massive problems with Usenet streaming through Eweka and Treasure-Maps in the last days?

A lot of streams are facing the same problem for a few minutes at a time in the last days...

u/SherbertPrior9101 — 8 days ago

How to watch usenet without getting cache?

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

reddit.com
u/Ancient-Subject-1949 — 8 days ago

sources for scene releases

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.

reddit.com
u/tatere — 9 days ago
▲ 11 r/UsenetNoRules+2 crossposts

Bonded three WireGuard tunnels into one gateway with per-client pinning — now open source (AGPL)

A single WireGuard tunnel is one path. If you have more bandwidth than one tunnel can carry, or several clients that each want their own exit, today's options are a container per tunnel or a pile of hand-written ip rule scripts.

I wrote a small daemon that owns the routing table on a gateway box and gives you two modes per client:

  • pin — one client, one tunnel, permanently
  • bond — spread a client's connections across every live tunnel (ECMP)

The config is the whole interface:

tunnels:
  - /etc/wireguard/wg0.conf
  - /etc/wireguard/wg1.conf
  - /etc/wireguard/wg2.conf

clients: 172.20.0.0/24

routes:
  pin:
    - 172.20.0.10
    - 172.20.0.12
  bond:
    - 172.20.0.20

Four things that took a while to get right:

  • fib_multipath_hash_policy=1 is mandatory, and the kernel default is wrong. At 0 the hash is L3-only, so every connection to a given server rides one tunnel. Torrents spread anyway, so a torrent-only test hides it completely.
  • A tunnel being up means nothing. WireGuard only rekeys when there is traffic, so liveness is time-since-handshake. Interfaces sit up for hours blackholing whatever you route into them.
  • Deleting an interface silently empties the table that routed through it — while the ip rule pointing at that table survives. A tunnel that drops and comes back leaves its pinned client with a rule to an empty table: every rule present, plan unchanged, exactly one client dead.
  • Client traffic must be masqueraded onto the tunnel's own address. Cryptokey routing at the far end drops any source that isn't the address your provider issued, and it fails silently — handshakes fine, counters move, requests vanish.

Fails closed. No live tunnels means no path out, not a fallback to your ISP.

bondvpn leak-test drops every tunnel and probes from a throwaway netns attached to the client bridge — the same path a container's traffic takes, so the same rules apply. Probing from the host would prove nothing, since the kill switch lives in a forward-side chain.

u/Comprehensive_Ship42 — 7 days ago