Nyrima

Personal Video Cinema on Google Drive

Turn a Drive folder you can access into a private Chrome-extension cinema: original media bytes, folder-owned artwork, rich subtitles, and no Nyrima backend.

Documentation | How It Works | Architecture | OAuth Setup | Privacy Policy | Report an issue

Nyrima is a Chrome Manifest V3 extension for watching personal video libraries stored in Google Drive. You pair one Drive folder as the Nyrima root, and each child folder becomes a library in the lobby. Nyrima finds videos, sibling subtitles, and artwork files you place in those folders, then plays the media inside an extension page.

Nyrima is not a hosted video service. The current app has no Nyrima backend, transcoding server, analytics endpoint, or ad network. Media stays in Drive and streams from Google Drive APIs to the browser when the user opens it.

1. The extension page lists folders and files from Google Drive using either a user-provided Drive API key for public files or a user-provided Google OAuth client for signed-in Drive access.
2. The lobby turns child folders under the paired root into libraries with poster art from files such as Poster.jpg and Backdrop.webp.
3. The player prefers browser-native playback. For MKV files that need help, Nyrima can Range-fetch Drive bytes, remux supported streams to fragmented MP4 through Media Source Extensions, and render ASS subtitles with JASSUB.
4. Settings, watch progress, recent folders, credential values, and caches are stored locally in extension storage or IndexedDB. OAuth access tokens are mediated by the background service worker.
5. Sharing is optional. When the user publishes a Drive-created Shared/ folder, followers can read share metadata from Drive, comment through their own Drive comment stream, and import accessible targets into their own Drive with Drive server-side copy operations.

For the plain-language version of the full data flow, see docs/how-nyrima-works.md. For implementation boundaries and storage details, see docs/architecture.md.

• Pair one Google Drive root folder; each direct child folder becomes a library tile.
• Browse a cinematic lobby with recent libraries, pinned items, Continue Watching, stats, library search, filters, sort order, grouped seasons, grid mode, and list mode.
• Use folder-owned artwork: Poster.{jpg,png,webp} and optional Backdrop.* inside Drive folders. Nyrima does not fetch poster metadata from a third-party media database.
• Parse episode-style filenames and season folders for show grouping while still supporting movie folders.

• Play Drive media from the extension player with resume state, next-up autoplay, theatre mode, shortcuts, subtitle settings, audio-track controls, and a custom HUD.
• Prefer direct browser playback, then use the current MKV remux path for supported MKV video/audio combinations that need MSE.
• Support supported external sibling subtitles including SRT, VTT, ASS, and SSA, plus supported embedded MKV text subtitles.
• Render ASS/SSA typesetting through JASSUB/libass where the current subtitle path supports it.

• Create an app-owned Drive Shared/ folder with index.json share metadata and comments.jsonl outbound comments.
• Publish that folder only when the user opts into "Anyone with the link" read access.
• Follow another user's published Shared/ folder URL and sync entries into an Inbox.
• Import accessible shared videos or folders into Nyrima/Imports/<share title - timestamp>/ with Drive copy APIs.

Nyrima has two current Google Drive access modes:

The OAuth flow is current BYOK behavior. Nyrima uses chrome.identity.launchWebAuthFlow from the background service worker; it does not require editing an oauth2 block into the manifest. Follow docs/oauth-setup.md for development and tester setup.

npm install
npm run build

1. Open chrome://extensions.
2. Enable Developer mode.
3. Click Load unpacked and choose dist/.
4. Open Nyrima from the toolbar popup or the app tab.

1. Create or choose a Google Drive folder to be the Nyrima root.
2. Put one child folder inside it for a movie or show.
3. Put videos inside that child folder.
4. Optionally add Poster.jpg, Backdrop.webp, and subtitle files with a matching basename such as Episode 01.mkv and Episode 01.en.ass.
5. Pair the root folder in Nyrima and configure access.

For the full first-run path, see docs/getting-started.md.

npm install
npm run dev

Load dist/ unpacked after a production build when checking extension permissions, OAuth extension ID behavior, and Chrome loading errors.

Nyrima also has a separate public promo website. That site is the public distribution and information surface for the package upload/download path, installation help, product Q&A/FAQ, privacy policy, terms, support/contact, and reviewer/store-facing links.

The promo site is separate from the extension runtime. Public copy there should match the currently packaged extension and the policy/docs in this repository.

npm test

The current Vitest suite covers title parsing, subtitles, sharing stores, Drive import helpers, EBML/remux logic, AC-3 playback helpers, fragmented MP4 generation, MSE controller behavior, and the Node release-script toolkit. Browser extension integration, Google OAuth consent, real Drive permissions, and media playback against real files still need manual verification in Chrome.

Start at docs/index.md.

Engineering phase status stays in PHASES.md.

Future contributor and agent guidance lives in .claude/README.md: workflow, artifacts, system boundaries, reusable patterns, Nyrima styling, and Once UI integration notes. It complements the deploy docs above; it does not replace them.

• Media bytes flow from Google Drive to the browser. Nyrima does not upload media to a Nyrima server.
• Nyrima does not read browser cookies from Drive or other websites.
• OAuth tokens are handled through the background service worker and are not sent to the optional GitHub raw directory endpoint.
• Publishing a Shared/ folder makes share metadata readable by anyone with that folder link. It does not automatically grant access to the underlying target file or library folder.
• The detailed permission and data-use map is in docs/permissions-and-data-use.md.

MIT.