I don’t make the rules. If you’re on lemmy qnd nextcloud does exactly what you want you need to complain about it being “over engineered” or “bloated” because it does things you don’t need.

No, you have to complain about them. It’s the law.

Linus did 3 videos on “how to degoogle your life” and only 1 was taken down. That one told people how to circumvent YouTube’s platform and monetary system which violated the community guidelines.

It will stay up. Do you know how many YouTube videos there are badmouthing Google? They don’t care so long as you’re watching them.

Kids… You ever wonder how “rar” came about?

Usenet had limits on its text only post size as well.

Peers can connect to your subplebbit using any plebbit client, such as Plebchan or Seedit. They only need the subplebbit’s address, which is not stored in any central database, as plebbit is a pure peer-to-peer protocol.

Do I need a new plumbus or will my existing one work?

Uncompressed flac? That’s a shit ton of music…

This is the way. Ansible is underrated by the self hosting community.

ctrl+a and ctrl+e are from Emacs.

I once ran ‘chown -R root:root /’ in a misguided attempt to solve some permissions issues I was having. 0/10, do not recommend. It turns out a lot of system things aren’t root owned…

Running a stupid command and learning from it is part of the learning process.

You got the basic idea from other posters, but there’s also a lot of weird crap in there as well.

Basically you only need multiple IPs when dealing with services that only really operate on “well known ports”. DNS and SMTP being the usual culprits. For most home users there this is no big deal - even if you wanted to host those services it’s unlikely that you would need more than one ip to do so. HTTP solved this in '97 with HTTP/1.1 which allowed for host headers, which let’s a single server host multiple sites.

This isn’t something new that nginx solved. 😂

By “modern” do you mean “the late 90s”? HTTP 1.1 was adopted in '97 and allowed for the host header. NAT and port forwarding have been around since '94 - 2000ish.

Many services worked on any ports at the time as well. SMTP and DNS are probably the only ones that were (and remain) difficult to run on non-standard ports.

I guess that’s “a lot simpler” than 6 lines of config?

Kids seem to think host name based routing is "new’… It worked fine in the 2000s with Apache.

It’s not uncommon to have your Dockerfile curl https://host/file.tar.gz and then tar xvf file.tar.gz into the filesystem somewhere.

You don’t want to use snaps in docker containers. They need systemd and stuff that are going to be a real pain to get working.

Generally speaking I would avoid combining critical networking infrastructure with other services. Just from a reliability standpoint.

Let your router be just a router. Simple = reliable.

“I use Nix, btw”

You say “The Windows Memory Subsystem” not “The Windows Subsystem for Memory”.

Windows Linux Subsystem would likely be most clear.

I build my infrastructure with the terraform, Ansible and helm charts. The code is it’s own documentation as well as comments in that code explaining why I’ve done things if it’s not obvious.