Start with Invidious
- Obtain the HTTPS address of an Invidious instance you operate or are authorized to use.
- In Rin, name the profile and enter that address in the required Invidious field.
- Run the compatibility check. Rin verifies instance health and a fixed, non-personal discovery search before saving.
- Use Rin anonymously, or connect a separate Invidious account for subscriptions, feed, and watched state.
Optional capabilities
- Materialious
- Adds encrypted progress and richer cross-device history. Rin verifies it when you sign in.
- Live resolver
- Adds the configured instance's native live-stream compatibility route.
- SponsorBlock
- Adds optional community-marked segment skipping. It is off on a fresh public install.
Invidious media proxying is also off on a fresh public install. Both settings remain explicit in Rin.
Importing a profile
A .rinprofile document is small JSON containing a schema version, profile name, and HTTPS endpoints. Opening one displays a confirmation naming its Invidious host. Credentials and viewing data are never part of the format.
Compatibility baseline
The initial tested baseline is Invidious 2.20260723.0 and Materialious 1.17.9. Other compatible versions may work. Rin reports failures by capability so an optional service outage does not erase anonymous discovery or local history.
Know your operator
The server operator can observe requests that reach that server. Review its policies and access controls before signing in. Rin does not certify public instances and does not provide a fallback server.