I agree with everyone here that self-hosting email is never easy, but if you still decide to go down this route then here are two tips that I personally found very helpful, especially when you decide to host it at home:

The first is to get an SMTP relay server. That’s just another mail server that yours can log into to actually send its mail, just like an email client would. That way you don’t have to worry about your IP’s sending reputation, because everyone will only see the relay’s reputable IP.

Second is to configure a Backup MX. That’s an additional MX DNS entry with lower priority than the primary, and it points to a special mail server that accepts any mail for you and tries to deliver it to the primary server forever (or something like an entire week). So when your primary server is unreachable other sending servers will deliver mail to the backup, and it delivers the mail to the primary as soon as that’s back online.

You can get these as separate services, but some DNS providers (like Strato for example) offer both with the base domain package. It makes self-hosting an email server much simpler and more reliable in my experience.

Welcome to the Linux community. :)

You will probably never understand everything about Linux and all of its included and associated systems. That’s completely fine, no one does! That’s why we are many, and it’s what asking for advice or help is for. You can just learn whatever interests you at your own pace, and know that there will always be interesting things you haven’t seen yet.

I really like the idea of creating a decentralized network that has a fair monetization model built right in, instead of relying on donations like the Fediverse. Crypto got a very bad rep, but this kind of stuff is exactly what it’s good for imo.

It also has some core features that are missing from other similar messengers, like multi-device sync. And lastly, the devs seem pretty capable and open as well. They are very transparent with their work and seem to have the right ideas about where things should go and which trade-offs to make. E.g. their reasoning for not using the Signal protocol seems solid to me.

So I’m hopeful, but time will tell if it all works out.

I’m transcoding everything to 320kbps MP3s. It’s much much smaller than flac, and I can’t hear the difference even if I try.

Trying to finish the Horizon Forbidden West story, but it’s a bit meh. Really sad about that! The HZD stories were great, and the world is as beautiful as ever, but I stopped caring at some point with the newest one. Other than that, I just bought the Age of Wonders 4 season pass and am trying out the new races and traits.

Fedora, I usually wait 1-2 weeks for the last bugs to be found+fixed and extensions to catch up, and then just upgrade in-place. Haven’t had a major upgrade problem for years now, it’s mostly as smooth as any other offline update. And I don’t feel like I have to reinstall the OS every few years on Linux either.

One of us One of us One of us! :)

deleted by creator

Idk when you checked, but they work pretty well now. Not quite on par with Google Docs, but the closest thing I know.

No! I prefer ______, and you are WRONG for thinking otherwise!

I can’t recommend Synology enough! They make it as easy and painless as possible to own your data again.

Hier geht es aber in aggregierte Geschäftsdaten.

Gilt für beides. Es gibt ja schon Integrationen, bei denen man einfach GB von Daten jeglicher Art hochlädt, damit die KI darauf Zugriff hat und maßgeschneiderte Antworten geben kann. Und je mehr die KI versteht, desto mehr ist man gewillt hochzuladen, weil es ja nützlich sein könnte.

Ja so verstehe ich das auch, es ist nur etwas ungünstig formuliert. Es geht darum aus den Daten alle nützlichen Informationen zu extrahieren, nicht “alle Daten” zu sammeln. Wobei sie mit den sehr persönlichen KI Assistenten natürlich trotzdem auf dem Weg dahin sind.

Maybe take a look at Appflowy. It’s another Notion clone like Anytype, but it’s much easier to selfhost.

No, it really doesn’t. That’s like creating a bot that buys and sells company shares automatically, and saying the stock exchange has a vulnerability because your bot makes bad decisions.

I just set up a Vouch-Proxy for this yesterday. It uses the nginx auth_request directive to authenticate users with an SSO server, and then stores the token in a domain-wide cookie, so you’re logged in across all subdomains. Works pretty well so far, you don’t even notice it when you’re logged in to your SSO provider.

But you do have to tell the proxy where you want to redirect a request somehow, either by subdomain (illegal.yourdomain.com) or port (yourdomain.com:8787) or path (yourdomain.com/illegal). I’m not sure if it works with raw IPs as hosts, but you can add additional restrictions like only allowing local client IPs.

In my special case I’m using the local Synology SSO server, and I have to spin up an additional nginx server because the built-in one doesn’t support auth_request.

What’s absurd is this crypto maximalist take.

You can’t just make up your own permission and punishment system, and then expect the legal system to just step aside and let it handle all disputes, especially when it comes to fraud. That’s like founding your own city in an existing country, and declaring all existing law obsolete. I know some people think this is a real possibility, but the real world doesn’t work like that.

IANAL and all, but bad/unfavorable contracts and literal deception/fraud are two different things, at least in the legal system. Not everything that’s technically possible is also allowed, obviously.

Compare it to using a security flaw to hack into a system. Technically you’re only using the official API, maybe in unusual ways, but still. But you’re doing it in bad faith and causing harm, maybe pretending to be someone you’re not or injecting fake data into the system, and that can make a difference.

It’s not. They tricked some MEV-Boost bots into doing bad trades.

Here is a more detailed explanation of the exploit.

The Pepaire-Bueno brothers exploited a bug in MEV-boost’s code that allowed them to preview the content of blocks before they were officially delivered to validators, according to the indictment.

The brothers created 16 Ethereum validators and targeted three specific traders who operated MEV bots, the indictment said. They used bait transactions to figure out how those bots traded, lured the bots to one of their validators which was validating a new block and basically tricked these bots into proposing certain transactions. […]

So hardly an attack on any core system of cryptocurrencies.