I'm a big proponent of self-hosting, right to repair, and rolling your own whatever when you can. That probably started as teenage rebellion that got baked in - I was lucky enough to read both Walden and The Hobbit during a week-long cyclone lockdown several decades ago - but I suspect there's a non-trivial overlap between that space and privacy-minded people in general.
My endgame is a self-sufficient intranet for myself and family: if the net goes down tomorrow, we'd barely notice.
I also use LLMs as a tool. True self-hosted equivalence to state-of-the-art models is still an expensive proposition, so like many, I use cloud-based tools like Claude or Codex for domain-specific heavy lifting - mostly coding. Not apologising for it; I think it's a reasonable trade-off while local hardware catches up.
That context is just to establish where I'm coming from when I say this caught my attention today:
https://support.claude.com/en/articles/14328960-identity-verification-on-claude
To be accurate about what it actually says: this isn't a blanket "show us your passport to use Claude." Not yet.
The policy as written is narrower than it might first appear.
My concern isn't what it says - it's that the precedent now exists. OAI will do doubt follow suite.
Scope creep is a documented pattern with this kind of thing, and "we only use it for X" describes current intent, not a structural constraint.
Given the nature of this community, figured it was worth flagging.
Currently my setup for YouTube In jellyfin is pretty basic (but it works well)
Its one complex yt-dlp script that runs ecery hour, reads a list of channels from a txt file. Rss to check the last 2 vids per channel, if there not downloaded already (log with vid ids per channel) it starts to download on high quality preset, filter out shorts and “live”, if the result is getting above a certain size it aborts and tries again with lower quality preset.
I don’t have a system to auto dele yet cause the script is only for my favorites. For everything else or that uploads to regularly i host a local invidious.
But google really hates invidious and it breaks frequently, even got my original residential ip banned. I may take a look at tube archive cause i would prefer download and delete as a more stable flow.
Something else i am experimenting with is using the same data in multiple systems. My music collection is a proxmox dataset but as long as the read rights are good i see no reason why jellyfin can’t also read those files.
The output folder of ARM used to be its own library in jellyfin on my first server.