

Do you really think a self hosting community has no idea how difficult and time consuming self hosting email is?


Do you really think a self hosting community has no idea how difficult and time consuming self hosting email is?
If you set up resources correctly on his netbird network it effectively is a split tunnel. You don’t have to route anything through it but his “file shares and stuff”.
I have a rather gnarly nested double nat within my house where the homelab is isolated behind it’s own separate firewall and have some limited resources on both. It’s been perfectly serviceable.
I believe I have a resource of *.whathaveyou.net on the netbird gateway inside the network and no default route. If you do have that default route I believe you can have it as a separate resource and disable it.
Self-hosted netbird is pretty incredible to be honest.
Traditionally I open a README.md in the dir the application lives in after I configure something I will open my browser history, and dump every link I clicked into the file.
I then copy paste a choice selection of my shell history into the file.
This is the bare minimum. It’s easy to do, takes like 5 minutes, and you will be happy to have it in 8 months. I would make the argument that anyone who tells you to do anything else can suck it. Do the readme first, any “better” documentation second.
Getting Into the habit of doing this matters more than a good documentation system. You will be lazy and try to get around to documenting something later. Don’t let it be later. Shitty link dumps are still gold mines for your future self


My personal suggestion would be to add initcall_blacklist=algif_aead_init to your kernel arguments. Ebpf is cool, but not a very trivial solution.
I understand the suggestion might apply to a random, unspecified distro but I disapprove of both the exploit authors and the general Internet suggesting fixes that don’t apply to every distro (including copy.fail’s AI slop RHEL distro that doesn’t exist) without caveating it.
The kernel module blacklist won’t work for every situation, if you’re not being specific in telling people where it applies, it’s best to suggest a solution that actually works regardless of distro or explain how to validate when it applies but nobody is doing that.


I continue to protest against this claim. Blacklisting the kernel module does not work for a bunch of distributions including Alma, Rocky, RHEL and others because they have this module built into the kernel. There’s no module to remove. You must use a syscall blacklist or similar mechanism to disable this.


If you’d like evidence of the toxic or extreme side of Lemmy, it’s not hard to find. Are we really disagreeing that this is a problem with Lemmy? Regardless, you’re misrepresenting OP with the “declare the other side is unbiased”.
This conversation started started with pushing back on the idea of using Lemmy as a solution to small site discoverability. The toxicity and social aspects are perfectly relevant.


He’s at -5 at the moment. Depending on what instances you have blocked, you’re going to see different amounts. It doesn’t mean those people aren’t there.



Even here, the guy you’re responding to is getting down voted to oblivion (for Lemmy anyways) for an opinion that I have echoed elsewhere and gotten the opposite response.
Not having the majority opinion of this community seems to mean downvotes too. The only real difference is that reddit has enough staying power for people to put up with it.


That would be true worst case, but you’re never running inference 24/7. It’s no crazier than gaming in that regard.
Have you spent any time in these ‘home lab enthusiasts’ spaces? Nobody here is suggesting that you should go and self host email. Nobody is making it sound easy. In fact if you look at posts talking about email, almost every time the subject of email comes up you have a significant portion of the community saying it’s outright not worth self hosting email. It’s such a time consuming and opaque process to figure out why email isn’t being sent or received that few do so.