WhatToWatch

A like adds one point to every genre, the director and the top three actors of that film. A dislike removes one. Ranking a film is then a sum, with the director counting double because a director match is rarer than a genre match and says more. Collaborative filtering would be better with a hundred thousand users and is worthless with the number I have, so the choice was between a model I could not feed and forty lines I can read. Being able to explain any single position in the feed has been worth more than any accuracy I gave up.

export function scoreMovie(
  movie: { genreIds: number[]; director: string | null; cast: string[] },
  profile: TasteProfile,
): number {
  const genreScore = scoreGenres(movie.genreIds, profile)
  const directorScore = movie.director ? (profile.directorWeights.get(movie.director) ?? 0) * 2 : 0
  const castScore = movie.cast.reduce((sum, name) => sum + (profile.castWeights.get(name) ?? 0), 0)
  return genreScore + directorScore + castScore
}

Films are fetched from TMDB per request and thrown away. Supabase holds accounts, saved films, ratings and declared subscriptions, and nothing else. That removes an entire class of work: no import job, no staleness, no availability data going quietly wrong in a table. The bill is that ranking can only see films that already made it into the request, so choosing the candidates matters more than scoring them. Sixty per cent of each page goes to the best genre scores and forty per cent stays random, because a feed that only shows you what you already liked stops being a discovery feed within a week.

Anything prefixed for the browser is compiled into the bundle, not read at boot. Changing one means rebuilding the image. Obvious in hindsight, and a genuinely confusing afternoon the first time a config change appeared to do nothing.

Pointing the tunnel at the reverse proxy produces an infinite redirect loop: the proxy upgrades HTTP to HTTPS, the tunnel arrives over HTTP, and they argue forever. The tunnel goes straight to the container; public TLS is the tunnel's job.