Skip to content

MaiPai Home 0.6.0

Choose a tag to compare

@JesseWebDotCom JesseWebDotCom released this 03 Sep 04:29
· 2 commits to main since this release

New here? Install MaiPai Home · Already running it? How to update

[0.6.0] - 2026-09-03

Changed

  • YouTube playback survives a blocked home address on its own. When YouTube
    starts asking your server to "sign in to confirm you're not a bot", the
    server now goes quiet for real: no background fetching, no hover previews,
    no warming, nothing anonymous at all, so YouTube can trust the address
    again. It checks back every six hours with a single request instead of the
    old thirty-minute burst, which turned out to be what kept the block in
    place. Videos keep playing through the household account in the meantime.
  • Your server keeps a signed-out YouTube session of its own, made by opening
    one video a day in a browser on the server, and uses that for playback
    before it ever touches the household account. No account, no name, no
    history attached to anyone.
  • The household YouTube sign-in is treated with more care: the server no
    longer reopens it every few hours (that was what kept breaking it), signs
    in again only after the session has failed twice in a row, and never more
    than once a day. If it keeps failing you get one notification instead of a
    loop of automated sign-ins.
  • Everything the server asks YouTube for is counted against one daily
    household budget sized to what a person would do, with a smaller slice for
    background work (feeds, transcripts, warming). Background work stops first;
    a person pressing play always has room.
  • The piece that proves to YouTube that video requests come from a real
    player is now the maintained one (bgutil), set up and kept running by the
    server automatically. The previous one had been abandoned upstream and no
    longer produced tokens YouTube accepts.

Fixed

  • Videos that resolved fine but then failed with a 403 partway through, and
    hover previews that said "available" and then died, both caused by the
    old token provider.