Thanks, good info. Never had any problems with pfsense or opnsense with Intel server NICs personally. Other than being fried.

In the country I live I can literally go to jail if I voice opinions other than “unprovoked Russian aggressive attack”. Presumably the more timid local Lemmy instance owners would fear liability.

Not exactly a new user. My lemmy.ml account is three years old.

Time to get serious about running my own instance. I now have to wonder what kind of political opinion I might voice which could make the instance operators liable. This is not tolerable long-term.

Same. Quad port Intel NIC.

I had no problems communicating a higher limit. They are not AWS but you can get 100s of instances.

Happily, I’m abnormal that way. I also dabble in PV DIY. Building houses from scratch, no. Servicing a modern car is also not worth it. Sadly, no open source EVs yet available.

HA for personal MTA is way overkill, just run a second instance with higher MX record value. Antispam is a given, backups are snapshots, maintenance is just system updates. Of course, you could just run an appliance which does it all for you. I’d say it’s way easier than in 1990s.

Email in the 1990s and email in 2020s is the same if you’re running your own MTA.

Connect your server to the Fritzbox via a patch cable.

Your profile contains your post history to many of your communities.

I’m pointing out that if you’re going to the trouble of hosting your own instance you could as well allow some convenient number of random users to register. It would erase most of your signal and help distribute the load and exposure to specific legal compartments.

Your profile is also public. An instance with few 10 subscribers erases much of the information.

Load leveling. Specific policies. More control and performance, if it’s your own instance.

Are the alternatives feature-complete in regards to GitLab CE?

Do not use WLAN, use wired Ethernet. What’s your upstream? It’s limiting the rate you can serve the content.

Encrypted file systems requiring secrets at mount time can make seizing physical servers harder. It’s more difficult with the cloud hosters, since these likely have an API for law enforcement.

It’s Jerboa.

I presume federation does not propagate diagnostics available in the instance logs. We definitely need privacy-hardening docs for running Lemmy instances.

It should be not part of Lemmy’s server side code. Actually even integrating current image support is ill advised. It should have been an optional microservice.

All is a good place to find leads for subscribed. Browsing communities seemed to be limited to the instance.