Skip to content
tanmayhuttPublic

About

A private two-person experience for comparing YouTube tastes with read-only data.

Resources

Stars

1 star

Watchers

0 watching

Forks

Repository files navigation

Blend

Blend is a private two-person experience for comparing YouTube tastes. Each participant connects their own Google account, reviews the data-sharing notice, and grants read-only access. Blend turns subscriptions, liked or saved videos, and playlists into a guided shared reveal.

Blend does not access watch history and does not change either YouTube account. Compatibility scores, interest labels, and recommendations are generated by Blend and are not YouTube or Google metrics.

The product and repository are named Blend. YouTube is the data source and supported platform, not part of the product name. Blend uses Google OAuth 2.0 and YouTube API Services and is not endorsed by or affiliated with YouTube or Google.

Product flow

  1. The host connects Google and prepares a current YouTube snapshot.
  2. Blend creates a single-use invitation that expires after two hours.
  3. The guest reviews the exact sharing boundary and connects separately.
  4. Both participants can view the same guided reveal: account profiles, compatibility signal, shared finds, differences, recommendations, and a shareable summary.
  5. Account settings provide local sign-out, Google disconnection, and permanent account-data deletion.

Stack

  • React, TypeScript, Vite, Tailwind CSS, and Framer Motion
  • FastAPI and MongoDB
  • Google OAuth 2.0 and YouTube Data API v3
  • Docker deployment behind Caddy

Self-hosted deployment

Blend runs in /home/ubuntu/tanmay/blend on the Ubuntu host. Docker publishes only 127.0.0.1:5060; host Caddy provides public HTTPS. MongoDB Atlas remains the database, using the existing database name and credentials.

Provide the backend environment values in .env.production with mode 600. Never commit this file. Compose fixes the production URLs and disables debug and fallback authentication. The frontend uses same-origin /api requests.

docker compose up -d --build
docker compose ps
curl -fsS http://127.0.0.1:5060/api/health

Append deploy/Caddyfile.blend to the host Caddy configuration only after backing up and validating it. Never replace the shared configuration or remove other sites. Point the blend DNS A record to 15.206.247.203. Caddy obtains HTTPS after DNS resolves to this server.

The Google callback remains https://blend.tanmaytiwari.me/api/auth/callback. Pushes to main run the automated Deploy to Ubuntu GitHub Actions workflow using a restricted SSH deploy key.

Local development

The frontend requires VITE_API_URL. The backend requires MongoDB, Google OAuth, and JWT environment values documented in backend/.env.example.

cd frontend
npm install
npm run dev
cd backend
python -m pip install -r requirements.txt
uvicorn main:app --reload

Security and data lifecycle

OAuth handoff codes are single-use and expire after two minutes. App access tokens are short-lived; refresh tokens are random, hashed in storage, and rotated when used. Invitation links expire after two hours. Google credentials and cached API data are stored server-side, not embedded in comparison links. Users can revoke Google access or delete their stored account data from Settings.

See the public Privacy Policy and Terms for the complete user-facing disclosures.

About

A private two-person experience for comparing YouTube tastes with read-only data.

Resources

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages