SEL-Filtering-and-Sorting is a tuned AIOStreams template for Stremio users

A configuration set, not an addon

The repository description calls it a page featuring AIOStreams templates and AIOMetadata configs for an all-in-one streaming setup, and the directory listing matches that. There are `AIOStreams Templates/`, `AIOMetadata Configs/` and `AIOStreams-SyncedURLs/` directories, a `Tamtaro-All-Templates-for-AIOStreams.json` file, images, and a `CHANGELOG.md`.

There is no code to build and no package to install. What the author did was write a configuration for AIOStreams, an addon host for Stremio, and publish it so other people can import it and adjust it.

The mechanism underneath is the Stream Expression Language, which the README links to the AIOStreams wiki page describing it. SEL is what makes the filtering interesting. A traditional addon config filters with blunt rules, and the README names the two it wants to avoid, `Exclude Uncached` and simple `Result Limits`, because both throw away results rather than ranking them.

The stated preference is dynamic filtering that tightens when lots of results exist, putting 1080p and 4K first, but keeps 480p and 720p fallbacks when the higher resolutions are not there. That is a different goal from filtering. Filtering decides what is allowed, ranking decides what you see first, and this setup is mostly about the second.

The history behind it is also stated. The author says it began as a personal project during the early v2 AIOStreams betas, when he wanted a single config he could share with family and friends, with mid-resolution options for slower devices and premium remuxes for his own setup in one template.

Importing the template is a URL and a menu path

The setup path is short, and it has a detail that catches people out, which is that the template is not served from GitHub.

The address to use is the author's own host, and it is what a self-hoster adds to their instance.

https://git.tamtaro.de/complete

For a self-hosted instance, the README describes the path as Dashboard, then Ctrl K, then Templates URL, and entering that address there. For a public instance, the README links a list of instances and a set of direct links that carry the template in the query string, so clicking one opens the configure page with the template already attached.

The import itself is then either browsing or pasting. In AIOStreams the path is About, then Get Started, then Browse a Setup, where the entry appears as the Tamtaro Complete SEL Setup. The alternative is Save and Install, then Import Template, then paste the same URL.

The README recommends starting with that complete setup, because it has options for both debrid and usenet users and for P2P users, and it says to select your services as part of the flow and follow the customization steps that appear. TMDB and TVDB credentials are required for matching, bitrate and related features, which is worth noting because that is an external account requirement, not just a configuration toggle.

The last step is to load the template, save your AIOStreams instance and add it into Stremio or Nuvio.

The README also recommends a nightly instance over a stable one, arguing that nightly is just as reliable and carries the latest unreleased features, while making clear that any instance works and that a list is available in the AIOStreams documentation.

What the filters actually do, according to the changelog

The changelog is the most informative document in the repository, because it is where the filtering rules are described in plain terms rather than as a UI.

The most recent entry shown is version 2.0.6, dated March 3, 2026, and its first line is the one that explains the design.

2.0.6 (March 3, 2026)
- update: all passthrough streams under Passthrough Options will now bypass all SEL filtering limits (like those set under Additional Limit Options)

Passthrough is the escape hatch. A stream marked as passthrough skips the limits the template applies, which means the limits are defaults rather than hard constraints, and a user who knows what they are doing can opt out per stream.

The same entry records a fix to the cached sort, where language and SEL score are removed from it when set to no boost, which tells you that the sort has separate lanes, one for cached results and one for uncached ones. It also adds a 1080p remux filter contributed by another user, and a keep custom SEL scores option under the misc options header, which allows manual edits to the ranked stream expressions to survive.

That last feature is the most revealing. If the template overwrites your custom scores on every update, tuning is pointless, so the option to preserve them turns the configuration from something you consume into something you own.

The previous entry, 2.0.5, records fixes for the anime only language pin syntax, which was causing an error on saving, and for SEL URLs being overridden in a partial template when no SEL had been selected, plus new passthrough variants. The credits in parentheses show that several changes came from other users reporting problems in the AIOStreams Discord.

Catalogs are deliberately left out

One design decision is stated prominently enough to be worth its own section, and it is about what the template does not contain.

The README says the AIOStreams template does not include any catalogs, and explains the reason, which is that many people prefer AIOMetadata, a separate addon from AIOStreams, for that. The reader is pointed to the AIOMetadata section of the same page for metadata and catalog management.

So the repository is split in two halves. The AIOStreams side handles the streaming side, the filters, the ranking and the expression configuration. The AIOMetadata side handles the catalog side, and the JSON files there can be imported with or without anime support through trusted AIOMetadata instances.

The `AIOStreams-SyncedURLs/` directory sits alongside both, which is a third category of artefact, a set of URLs that are kept in sync.

The reason to pay attention to this separation is that a single config that does everything is convenient until it is not. Once the catalog side is owned by a separate addon, the metadata provider, the filters and the streamer are three pieces that can be replaced independently, and the streaming configuration is the part that keeps getting tuned while the catalogs stay as they are.

The README also points at the upstream resources the setup depends on, among them the ranked stream expressions project, AIOStreams itself and the AIOMetadata project, with links to each. That is a reasonable way for a config repository to be built, since the heavy lifting lives in those projects and this one is the curated combination.

What the repository does not tell you

There are gaps, and a reader should know where they are before relying on the setup.

The first is the licence. The project carries no recognised licence identifier, and there is no licence file among the top-level entries, which are the workflow directory, the three content directories, the changelog, the readme, the all-in-one template JSON and the image folders. Without a licence, the default position is that the configuration is not licensed for reuse, and the README says nothing about that.

The second is the versioning. The repository has no GitHub releases, and the version numbers live in the changelog as prose, with 2.0.6 the latest entry shown and 2.0.5 and 2.0.4 before it. The template URL points at a single address, so the template you get is whatever is currently at that address rather than a version you can pin, and the changelog is the only record of what changed.

The third is the dependency on the host. The template lives at `git.tamtaro.de`, so the setup depends on the author's server being reachable, and a change there is not versioned in the repository you can read. A self-hoster who wants a stable setup has to accept that, or mirror the configuration themselves.

The fourth is the requirement for external accounts. TMDB and TVDB credentials are needed for the matching and bitrate features, and the README recommends a debrid service for the best experience, with a particular provider named as the current top recommendation. Whether that recommendation holds for you, and what your provider's terms are for sharing a setup, are decisions the project cannot make for you.

A maintained configuration with an unusual delivery model

The activity signal is positive. The repository is not archived, and the last push was on 2026-10-18, with a changelog that records fixes and new filters contributed by users of the AIOStreams Discord.

The delivery model is the unusual part. There is no package, no install step and no container. There is a JSON template on a personal host, a set of metadata configurations in the repository, and a README that explains the menu paths to import them. The whole value of the project is in the contents of that JSON, and the maintenance work is in keeping it current as AIOStreams changes, which the README frames as a long process of tinkering, testing and trading tips rather than a release cycle.

For a reader deciding whether to adopt it, the questions are concrete. Does your AIOStreams instance allow a third party templates URL, and are you willing to point it at a host you do not control? Do you want ranking that is opinionated, with 1080p and 4K first and remux filtering, rather than a flat list? Are you willing to read the changelog when the results change, since the rules are versioned only in prose?

And is the answer to all three yes, the setup is a reasonable starting point, because the alternative is spending an evening building the same expression rules from an empty configuration, which is exactly the problem the author started with.

Editorial conclusion

SEL-Filtering-and-Sorting fits a Stremio user on AIOStreams who is tired of a result page full of unusable streams and wants ranking that tightens when many results exist but keeps lower resolutions as fallbacks. Skip it if you are happy with the default addon behaviour, or if you cannot add a third party templates URL to your AIOStreams instance, since the template is served from the author's host rather than from GitHub. Verify first that your instance accepts the template URL, that the debrid or usenet service you use is selected correctly, and that the TMDB and TVDB credentials you supply are the ones the matching features expect.

Frequently asked questions

Official sources

1. Issues
2. README
3. Tam-Taro/SEL-Filtering-and-Sorting on GitHub