• 1 Post
  • 494 Comments
Joined 7 个月前
cake
Cake day: 2025年6月4日

help-circle






  • notabot@piefed.socialtoOglaf@discuss.onlineAhoy
    link
    fedilink
    English
    arrow-up
    8
    ·
    4 天前

    This is an important point to remember. Before you go to sea, you should always curse your legs, that who or whatever has them will continuously dance until they drop from exhaustion.

    It might backfire a bit, but look at the desperate expression on that whale’s face and tell me it’s not worth it.







  • It rather depends on what you mean by “encrypted email provider”. Proton don’t do anything magical, incoming emails arrive unencrypted and they just encrypt them for storage. Likewise, outgoing emails may be stored encrypted, but aren’t encrypted on the recipients end. In both cases the email is unencrypted at the remote party’s end.

    If you want encrypted email between you and someone else the solution is GPG encryption. It’s not too complicated to set up, but does involve both parties using it, so you’re probably not going to get your bank on board, for instance, but it works between friends. The other big advantage is that it works with any email provider, “encrypted” or not. The very nature of email means that the headers need to remain plaintext so that the mail can be routed, but even proton can see those on incoming or outgoing mails.

    Contrary to popular consensus, I’d say that hosting your own mail infrastructure isn’t too difficult if you are willing to make certain compromises. Hosting incoming mail is a case of deploying one or more SMTP servers that can only receive email for your domain and store it on an IMAP server. All these components are well documented (I like postfix for SMTP and Dovecot for IMAP). Register these servers as the MX records for your domain, and you have incoming email. Spam filtering is a separate issue to look into, but quite doable. Outgoing mail is slightly more tricky, but there are various well trusted SMTP relays you can use for that. I have used Amazon’s SES service successfully, and I’m looking at SMTP2Go, as they seem to have a free tier that woud be well suited to a personal email setup. Remember, the incoming and outgoing servers do not need to be the same, which seems to be what trips a lot if people up. You do need the appropriate SPF and DKIM records for the outgoing servers on your domain though.



  • Whilst I see your point from the advertisers perspective, ie, misleading the consumer can be profitable, it also makes it all the more necessary for advertisers to be forced, ideally through legislative means, to disclose asset theft. That way they’re all on a level playing field, and are disuaded from lieing about it.

    That fact that most “AI” output is garbage is not directly relevant, but the sourcing of the training data and lack of human oversight are.