rm -rf /home/*

You need the directory for the mount point.

If you punch someone on the nose, you can’t expect sympathy when they punch back. This isn’t going to produce the result Hamas was going for.

I’ll be the heretic here, but so far as I know you are only required to make source available when you distribute binaries. And for that matter, it doesn’t even have to be online just available upon request unless you’re using a derivative GPL that added online access as a clause.

I highly doubt the users of a web interface are required to be given access to source. There are multiple GPL-licensed web servers (I am well aware Apache is not btw) and I’ve never seen one embed a code link on every page.

Tl;Dr: Lemmy does it, but I believe it’s not required. Modify away if you so choose.

Windows 10 LTSC (for me) generally has uptime that is the equivalent of any Linux box. I’ve been using it to host Plex for several years - before hardware transcoding support in Linuxv was really up to snuff.

LTSC is what Windows should be. It’s a shame Microsoft doesn’t make it available (legally) to normal consumers.

I made a post that was similar a week or so back that was fairly controversial where I advocated changing how the federation protocol works. I’ve been thinking about it more, and I think I have a solution to your concern (and mine) that keeps the admins feelings about federation and not allowing one instance to dominate in mind.

On Reddit, especially old.reddit, when you search at the top you actually get two different search results: subreddits matching %string% at the top, posts matching %string% at the bottom.

We should mirror that. The current search should be modified in the same structure and pump the search string into https://browse.feddit.de/ or implement it’s process into the server code.

I think when someone types in android, getting a list of currently existing Lemmy communities with their respective populations and post counts is probably the easiest way to smooth out the learning curve.

Yes.

And to some of the child replies, I think there’s a question of scale that often gets overlooked. In all these discussions, there seems to be two different groups commingling: ones who just need 1-2 simultaneous streams, and ones who are doing true whole-house-plus systems.

I’m serving subtitles-enabled streams to (mostly) Roku clients - who need the server to burn in the subtitle track for some insane reason. It’s nothing for my Plexbox to be serving 6 simultaneous streams. A 4790K would definitely not cut it for me.

Honestly, don’t bother with a dGPU and get a 12th or 13th gen Intel Core chip with QSV. Intel quietly tuned it up to the point where it’s faster than nVidia’s NVENC engine even in the latest gen plus you don’t have mess around with the uncap streams hack and you’re transcoding through system RAM not dGPU RAM, so far less likely that your stream limit will be artificially constrained by memory limitations.

To answer the question you asked though, the nVidia NVENC is the best solution on a dGPU. It’s performance is largely the same across the same board generation, with one exception in the GTX 10X0 series. The absolute cheapest card you can lay your hands on that has an NVENC engine is the 1050TI.

The caveat is the 1070 and 1080 have two NVENC engines. It will double max number of streams in theory, however in reality you’re memory bound on those cards and it’s more like a 33% bump.

Here we go:

Example files

Any place you see <something>, you need to change it to fit and omit the <>. If something <matches> in two differet places <matches> like this, make sure they match when you’re done as well. Specifically, the postgres user and password in the lemmy docker file and the lemmy.hjson.

Finally, in Google drive the files end in .txt so you can view them. You’ll need to correct the file names when you download them if you intend to use them. You should have two docker-compose.yml, one in each of the two directories you create, and one lemmy.hjson.

From a fresh CLI Debian 11 install:

su
/sbin/usermod -aG sudo <user>
groups <user>
apt-get install sudo
cd /opt
mkdir npm
cd npm
(copy or create docker-compose.yml)
apt-get install docker-compose
docker-compose up -d
cd /opt
mkdir lemmy
cd lemmy
(copy or create docker-compose.yml and lemmy.hjson)
mkdir -p volumes/pictrs
chown -R 991:991 volumes/pictrs
docker-compose up -d
docker ps (verify containers are all running, grab ip address for lemmy container)
Configure port forwarding in npm for your lemmy container (npm should be accessible at debian_ip_address:81)
Remember to do the custom paths from the various guides. The lemmy port in this guide is 1234.

Please note I am not addressing federation or SSL or true hosting yet. I haven’t got that far yet. But if you can get the damn thing running, the last mile shouldn’t be too bad.

So I wanted to make a top-level post: I’ve got a set of example files, and instructions, that will work 100% of the time on Debian. What do you guys think would be the best way to share them? A post here and the files shared on Google Drive? GitHub? Definitely open to suggestions, but I don’t want anyone to struggle with it as hard as I have.

I did. I could never get ansible to work when I was setting up the same machine. If you know how to set the inventory file up for that, I’m all ears.