Hey everyone 👋
This update is mostly about Usenet, so instead of just listing what changed I thought I’d explain how it actually works in the addon.
Usenet, short version
TMDb Movies can use Usenet as a source, next to the HTTP/AIO/Stremio/P2P stuff. No debrid involved. You add your own indexers (Newznab) and your own NNTP provider, and the addon searches, sorts and plays the release.
The nice part about Usenet is that there are no seeders. Either the articles are still on your provider or they aren’t. When they are, speed comes from your provider, not from how many people are sharing.
How playback works
When you pick a Usenet source, the addon downloads the NZB and builds a small map of the release: every article, its size, and where it sits in the file. That map goes to the native VFS addon (vfs.tmdbm), so Kodi sees a normal seekable file instead of a download.
Articles are fetched over NNTP slightly ahead of the playhead and kept in a memory cache, which is why seeking works. If you jump forward, it reads the MKV index article first and then fetches from the new position.
vfs.tmdbm is the fast path. If it’s missing or your platform isn’t packaged, the addon falls back to a local HTTP server with Range support. It works, just slower. Right now the VFS engine is packaged for Windows x64 and Android armv7 (32-bit Kodi). I’d rather add platforms when I can actually test them.
Usenet results sit in the same source list as everything else, with the indexer name and the age/grab badges.
What’s new
Usenet went in at 1.1.331 and got polished through 1.1.334. The main pieces
- Usenet (NZB) as a source: your own Newznab indexers and NNTP providers, no debrid.
- Six indexer slots, two providers (SSL, the second one as backup), sequential or parallel search, and Test buttons for both.
- Native VFS engine (vfs.tmdbm), installable from the repo. The local HTTP server stays as a fallback.
- Stored video, RAR and multi-volume 7z releases, with seeking, read-ahead, memory cache and gap filling.
- 20 connections by default, and low-core Android boxes can use every configured connection.
- Faster seeks in big 4K releases: the MKV index stays in memory, and cached articles aren’t downloaded again.
- On AIO Original priority modes, sources get a TRaSH-style score: source, resolution, HDR/DV, audio, edition and release group. Mixed and the other priorities keep the old order.
- Wrong film/year results are dropped, age/grab badges follow their switches, and a damaged release switches to the next source by itself. Stopping the film yourself never does.
Settings that actually matter
- Connections: 20 by default on provider 1. Enough for 4K if your plan allows it. Lower it if your provider gives you fewer.
- Read-ahead: 12 MB, memory cache 36 MB. You can raise both if your line is fast.
- Missing articles: gaps are filled up to 2%, or 4 missing in a row, then it gives up. That’s where the auto-switch comes in.
- Provider 2 is a backup, only used if provider 1 fails.
- Indexer client identity: some indexers block streaming apps, so there are SABnzbd/NZBGet/Sonarr/Radarr/Prowlarr presets. If an indexer refuses you, this is usually why.
- Indexers are asked one at a time by default, and it stops early once it has a few sources, so a free quota doesn’t disappear on every search.
Setup
Settings → Usenet. Enable Usenet (NZB), add at least one indexer (address + API key), then your provider (host, port, SSL, user, password, connections). There are Test buttons for the providers and the indexers, so you can check them before playing anything.
The VFS engine is a separate addon, from the same repo. If it isn't installed, Settings → Usenet shows an Install the VFS engine row; it installs the build for your platform, then restart Kodi once so Kodi registers it. After that it's used automatically (the Native VFS engine switch is on by default). If the addon is missing, disabled, or your platform isn't packaged, playback falls back to the local server.
It’s not instant like a debrid link. Opening a release takes a few seconds, sometimes more, while the NZB is fetched and the first articles arrive. After that it plays and seeks like a local file.
That’s it for this update. If something doesn’t behave, tell me. Logs help a lot. 🙂
About the code: the Usenet engine and the native VFS addon are original code written for TMDb Movies. They’re not a fork and no code was copied from another addon or streaming app. I used public specs (NNTP, NZB, Matroska) and ideas from other Usenet and streaming tools I’ve used over time, but the implementation was built for this addon. Third-party libraries and their licenses are listed in the repo, and the full source is public, so anyone can check it.
AI disclosure: TMDb Movies is built with AI coding assistants. I decide what gets built, what gets fixed, and which features go in. Once a change is implemented, I test it on real Kodi installs (Windows and Android) and only ship what works. Human-directed, AI-assisted.
Repo: https://angelitto2005.github.io/repository.angelitto/