A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
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.
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?
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
Similar to Invideous, et al. You Tube front end.
I was gonna say, how is this different from invidious?
This can actually use Invidious as its backend if someone wants to.
Its basically just a more feature rich Invidious whata easier to deploy.
Yes, exactly.
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.
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.
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.
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.
Yeah if you are running a private instance, you look like legitimate traffic to Google.
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.
I can’t seem to prove I’m not a robot on the selfhosted docker install… shame. I’m stuck at “verifying…”
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.
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.