This post was deleted
Are you planning on sharing the source?
Replying to @eleijeep@piefed.social
I mean…if there’s interest? Just let me figure out those last four nagging pains in the ass and I will put it up. The thing itself is pretty simple lego: frontend, nginx config, SQLite/FTS search service, index-builder scripts, BRouter integration, route-anchor logic.
Right now, I have a few irons in the fire, including a fork called SmartTube Local that is turning into a passion project.
That one is basically: “what if YouTube was local-first, self-hosted and yt-dlp-backed, with the local archive integrated directly into the app and automatically kept up to date…so if the internet died, your kids might not even notice?”
…I just did google maps…why not take on Youtube next, amirite?
EDIT: here you go -
Replying to @SuspiciousCarrot78@aussie.zone
Have you heard of Tube Archivist?
Edit: ok i see you mentioned it in your Local Smarttube announcement post. Why doesn’t Tube Archivist fit your needs?
Replying to @hirihit640@sh.itjust.works
TubeArchivist is:
- heavy (Redis, Elasticsearch).
- doesn’t have a native TV app.
- will not play nicely with the Raspberry Pi (table stakes are 2 GB RAM, which is more than half my RAM budget).
I like TA a lot, but not for what I have in mind. What I have in mind should use about 100 MB of RAM, run as a systemd service, with videos served directly to the front-end via Samba, in such a manner that they are indistinguishable from the cloud sources when displayed in-app (well, apart from a core badge saying LOCAL).
I’m not coding a simple Jellyfin plug in.