The best way to reclaim your privacy is to own the infrastructure.
-
The best way to reclaim your privacy is to own the infrastructure.
I migrated my email to a hardened FreeBSD setup. Encrypted at rest via ZFS, isolated via Jails, and owned by me. Not a data-mining giant.
If you want to build your own communication hub, here is the blueprint:
#DigitalSovereignty #DeGoogle #Privacy #SelfHosted #BSD #Mailserver
-
undefined stefano@mastodon.bsd.cafe shared this topic
undefined 77nn@goto.77nn.it shared this topic
-
The best way to reclaim your privacy is to own the infrastructure.
I migrated my email to a hardened FreeBSD setup. Encrypted at rest via ZFS, isolated via Jails, and owned by me. Not a data-mining giant.
If you want to build your own communication hub, here is the blueprint:
#DigitalSovereignty #DeGoogle #Privacy #SelfHosted #BSD #Mailserver
@Larvitz I really wish e-mail hosting was simpler. That sounds like a lot of work to set up properly and then there is maintenance. Thanks for posting it.
-
The best way to reclaim your privacy is to own the infrastructure.
I migrated my email to a hardened FreeBSD setup. Encrypted at rest via ZFS, isolated via Jails, and owned by me. Not a data-mining giant.
If you want to build your own communication hub, here is the blueprint:
#DigitalSovereignty #DeGoogle #Privacy #SelfHosted #BSD #Mailserver
@Larvitz to be useful, it needs to be either one click install or equally easy. This is only useful to people who are skilled enough to figure it out. There needs to be a beginner friendly way to do something like this.
-
@Larvitz to be useful, it needs to be either one click install or equally easy. This is only useful to people who are skilled enough to figure it out. There needs to be a beginner friendly way to do something like this.
@ailurocrat there’s several „one click“ solutions with Linux. Mail-in-a-box (MIAB), Mailcow, mailu.io and many more.
My setup is more meant as a blueprint for people who want to learn, having deeper understanding and proper control and who’re willing to „getting the hands dirty“.
-
@Larvitz to be useful, it needs to be either one click install or equally easy. This is only useful to people who are skilled enough to figure it out. There needs to be a beginner friendly way to do something like this.
@ailurocrat @Larvitz This is absolutely an industry wide problem in tech. Everything in tech is built for techies with normies as afterthoughts.
It results in "relatively easy" and tricks the techies into believing the normies are all idiots. They're not stupid, they just spent their skill points on other things.
-
@ailurocrat there’s several „one click“ solutions with Linux. Mail-in-a-box (MIAB), Mailcow, mailu.io and many more.
My setup is more meant as a blueprint for people who want to learn, having deeper understanding and proper control and who’re willing to „getting the hands dirty“.
@Larvitz @ailurocrat mailcow is great
-
@ailurocrat @Larvitz This is absolutely an industry wide problem in tech. Everything in tech is built for techies with normies as afterthoughts.
It results in "relatively easy" and tricks the techies into believing the normies are all idiots. They're not stupid, they just spent their skill points on other things.
@gooba42 @ailurocrat @Larvitz The problem with engineering is it's a specialised field and everything is built with engineers in mind, with normies as afterthoughts.
Same applies to anything else.. law, cooking, building etc. -
@ailurocrat @Larvitz This is absolutely an industry wide problem in tech. Everything in tech is built for techies with normies as afterthoughts.
It results in "relatively easy" and tricks the techies into believing the normies are all idiots. They're not stupid, they just spent their skill points on other things.
I appreciate your perspective on accessibility in tech. You're right that the industry often overlooks beginners, and I'm glad solutions like Mail-in-a-Box and Mailcow exist for those who need them.
That said, not every resource needs to serve every audience. This article was specifically written as a technical deep-dive for people who want to understand the underlying mechanics, whether they're learning system administration, troubleshooting issues those one-click solutions abstract away, or making informed decisions about their mail infrastructure.
There's room for both approaches: turnkey solutions for those who need email working quickly, and detailed technical guides for those building expertise.
Different resources serve different needs, and that's okay. The "normies" you mention aren't stupid at all, they're smart enough to choose the right tool for their needs, which often isn't a manual FreeBSD setup, and that's perfectly valid.
-
undefined oblomov@sociale.network shared this topic