The main difference between this project and the ones you listed is that this project includes a Plex installation out of the box. The other projects require you to connect to a separate Plex instance.

Cults tend to be defined by how they control their members. Cultures tend to form around similarities.

You need actual moderation to keep people safe.

Thanks for all the questions and I absolutely don’t think you’re being too negative! This was mainly made to scratch an itch I had, but I hope that other people find it useful too.

The main difference between this and plex_debrid is that this is set up out of the box to work without manual integration steps. You don’t have to copy the Plex API key around — simply sign into Plex and Overseerr, and my config script handles wiring your watchlist up to request content.

I’ve also built a high-quality media selection algorithm that I think is the best out there for getting the copies of media you want to make your users happy. Check out the docs on Media Profiles.

Putting everything in one container doesn’t necessarily break the mantra of using containers. I use containers all day at my job and in my personal clusters. What I’ve found is using tools like Docker Compose to distribute software makes it much harder for people to run my software on home servers like Unraid — and there wasn’t a technical reason I couldn’t bundle these into one container to make it easier. In this case, the services are pretty coupled and I don’t have much need to scale them up individually.

I haven’t built any automation for this yet, but my repo tracks the upstream sources for rclone, pms-docker, and Overseerr, and I’d like to pull in those updates as I cut new releases.

You’ve identified the main benefit – Debrid services provide cached torrents for “instant” downloads. Streaming straight from a Debrid service’s fileshare also means you don’t need to buy drives or additional storage.

When you say Wasabi, do you mean the hosted S3-compatible cloud storage service?

I don’t have any plans at the moment but I welcome anyone who would like to fork the project for this. Happy to try and make things easy for you.

I’m not denying that Mozilla has a history of poor governance. But they are the competitor to Google here. You need to consider these things in context to understand what anti-corporate means for the internet.

It absolutely matters. We need to consider that a right-wing actor is likely to exaggerate claims against an organization that is ostensibly socially-minded and represents anti-corporate interests, like Mozilla.

I do enough of this in the day job. I don’t have time to mess around with free hosting to save $20 a month.

I’m renting a beefy dedicated instance from HiVelocity for $55/mo.

Oracle is all fun and games until they lose your instance’s IP or data and don’t give it back because you’re a free tier freeloader.

Full disk encryption is something you really want to have when your computer is lost or stolen.

Thank you!

Please feel free! Source is on GitHub, it uses Astro with the Starlight template.

Thanks, this is lovely!

Thanks, I’ll try it out!

That’s a great way to attract stalkers.

If I still need to run a bouncer to get history scrollback, then no, I will not consider IRC.

Setting up a Lemmy server outside of the golden path of using the Ansible template is extremely difficult. I do this professionally and I couldn’t get federation working properly when running Lemmy on my Kubernetes instance.

Figuring out why federation is failing is very, very hard.

Lemmy requires a lot of resources to run. You need a VPS that’s at least $20/mo to work adequately under any load. Disk storage requirements for the DB are also rather high.

Lemmy 0.18.2 has some horrendous N+1 DB calls, e.g. one query per language (173 of them) when you create a new community. This hamstrings databases that are not colocated onto the same machine, e.g. neon.tech’s hosted pg db. I expect this will improve with time as the codebase matures, yet…

Instance administration tools are sorely lacking.

“It’s a good filter” is often just an excuse to not improve the UX. You hear this way more from open-source technically-inclined folks than you do from folks who care about building a product that people want to use.