• 1 Post
  • 92 Comments
Joined 1 year ago
cake
Cake day: July 23rd, 2023

help-circle
  • shrugal@lemm.eetoSelfhosted@lemmy.worldSimple mail server
    link
    fedilink
    English
    arrow-up
    8
    ·
    edit-2
    5 months ago

    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.









  • shrugal@lemm.eetoSelfhosted@lemmy.worldBeeper Self Hosting
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    7 months ago

    I started using their Signal and WhatsApp bridges today, probably one of the easiest setups I ever did. You just run a Docker container for every bridge, and login to your Signal/WhatsApp account by chatting in the app with the Matrix bot it creates.

    Literally takes like 5 minutes if you’ve used Docker before, and you don’t need a domain or forwarded ports or anything.


  • Nothing about what you just wrote has anything to do with closed source software though. You could just as well say that closed source helps them predict the future or draw shinier unicorns. It doesn’t!

    Maybe you mean tightly coupled, stripped-down, preconfigured or vertically integrated, but you can do that just as well with open source software. No one is forcing them to make a general purpose chat app or offer the ability to choose a different server. It’s just a matter of being able to see, verify and modify the code.

    differentiate above the competition […] charging for it

    This is the only thing that comes close imo. But they stated specifically that they don’t want to make money with the chat app itself, so it doesn’t really work as a justification. They could easily offer server-side premium features or create a closed source premium-only version or extension, it’s no reason to make the base app closed source.

    security theatre

    They don’t have to do that, and they don’t afaik. Matrix itself can do proper e2ee just fine, and Beeper is pretty open about the fact that bridges hosted by them have to break e2ee to translate between platforms. They’d only need theater if their closed source app actually has some bad code in it, which is kind of my point.

    Expanding to selling some user metadata, or sniffing the bridges, would be an extra

    Again: Their Matrix server and bridges are open source right now, and it wouldn’t stop them from doing what you’re describing.

    Too pedantic 😉

    I just can’t help it. 😜


  • the connecting with a majority of people using the same closed source platform

    The platform is open, including the part that connects to other closed source platforms. It’s just Matrix and open source bridges after all. And making the client app closed souce doesn’t help with any of that.

    I’m sorry if I’m a bit pedantic about this, but it seems like you’re describing an upside to closed source software that’s just not there.


  • You’re definitely right that people are a bit too doom-and-gloom about it, Beeper did do a lot of good over the last few years!

    But I also find it a bit odd that they talk so much about the importance of open source in messaging, and then release a closed source client without at least adressing the topic. Add the fact that they’ve been aquired by another company on the same day, and it starts to smell like another instance of openwashing.

    Idk, we’ll have to see how it plays out I guess.


  • I can answer that: it’s the “I don’t care about security as long as I can send memes and inappropriate messages to most people” experience.

    Closed source doesn’t help with that though, you don’t have to care about privacy in open source.

    except you do know that the bridges are decrypting all messages anyway

    They are working on on-device bridges that preserve e2ee, but making the client closed source kind of defeats the purpose here.




  • What is this “closed source experience” you are talking about? How would making the client open source hinder that in any way, especially when their stated goal is to earn money with premium features instead of the app itself?!

    Imo being open source is a VERY big deal for an e2e encrypted chat client! I don’t really care whether most of their stack is open if the app I’m actually using to type and encrypt my messages is not. This makes the whole thing look like a trick, pretending to be open when key parts are not.