So that the timestamp adjustment can be propagated via uploader or user comments across YouTube clients on all platforms… i.e. to avoid having to hardcode each adjustment for each ad on each video on every client
They’d still resolve via DNS to an address in ASCII though, right? Wouldn’t that only be an issue if ICANN didn’t have a monopoly on DNS registration? i.e what we already depend on for a semblance of convenience without totally compromising opsec
Could do that, or sideload the APK from https://repo.jellyfin.org/files/client/androidtv/