Watch YouTube privately - Materialious (github.com)
from Ward@lemmy.nz to selfhosted@lemmy.world on 14 Feb 15:45
https://lemmy.nz/post/34356264

Preview

Materialious is usable on Web, Android (TV too) & Desktop.

It can be used with Invidious or using its own YouTube backend.

Has its own account system with end-to-end encryption for subscriptions.

#selfhosted

threaded - newest

muusemuuse@sh.itjust.works on 14 Feb 16:51 next collapse

Help me understand what this does. It looks like it run on your own device and fetches YouTube videos you want to see, presenting them to you through its interface without ads and shit.

So I could throw it in my server and have my phone pull up its page and play content right?

Arkhive@piefed.blahaj.zone on 14 Feb 17:04 next collapse

Yes, exactly.

irmadlad@lemmy.world on 14 Feb 18:58 next collapse

Similar to Invideous, et al. You Tube front end.

taperi@piefed.social on 14 Feb 20:02 collapse

I was gonna say, how is this different from invidious?

Ward@lemmy.nz on 15 Feb 02:05 collapse

This can actually use Invidious as its backend if someone wants to.

Its basically just a more feature rich Invidious whata easier to deploy.

Ward@lemmy.nz on 16 Feb 13:04 collapse

Materialious can be deployed in a lot of ways.

It can be used purely as a Invidious frontend.

You can use it as a web server with its own YouTube engine and account system.

Or you can use it as a Desktop & Mobile app with or without Invidious.

Or you can even go into the advanced settings and choose when you want to use Invidious APIs or Materialious

irmadlad@lemmy.world on 14 Feb 19:35 next collapse

The thing about these front ends is that Google will eventually get around to blocking your IP. After many unsuccessful attempts that got ban hammered after a week or so, I finally got it to work. I piped it through Cloudflare Tunnels/Zero Trust. Haven’t had an issue. My deployment was the Invideous with companion app. The Companion app has been complaining about being unhealthy for ages now, but it keeps right on ticking. I don’t watch a huge number of YT videos. Usually my consumption is a tutorial here or there.

sam@piefed.ca on 14 Feb 20:10 next collapse

I’ve been running invidious on my home network for over a year now, no issues other than when YouTube makes changes that break for every inv user anyway.

Buck@jlai.lu on 14 Feb 20:25 next collapse

Yeah I don’t think any non public instance has any chance of being blocked. It simply looks like one user among millions to them.

irmadlad@lemmy.world on 14 Feb 21:56 collapse

Just my experience. Like I said, the only thing I use it for is to watch a tutorial without endless, unskippable ads just to find out the tut is trash.

Ward@lemmy.nz on 15 Feb 02:04 next collapse

Yeah if you are running a private instance, you look like legitimate traffic to Google.

nfreak@lemmy.ml on 15 Feb 13:18 collapse

I route my Invidious containers through Gluetun and it usually works fine. Occasionally I need to restart the stack to change the IP but for the most part it works great.

msokiovt@feddit.online on 14 Feb 22:02 next collapse

I tried it earlier, though the only issue has to do with VPNs, as YouTube hates them. Invidious doesn’t really work that well either.

Buck@jlai.lu on 15 Feb 20:56 collapse

I can’t seem to prove I’m not a robot on the selfhosted docker install… shame. I’m stuck at “verifying…”

Ward@lemmy.nz on 16 Feb 13:02 collapse

We altcha whats a proof of work captcha. Are you getting any console errors? You do have to wait for the captcha to complete for a bit too.