Skip Navigation

Posts
0
Comments
423
Joined
2 yr. ago

  • It's a misnomer mate... Like how r/trees isn't about trees and r/tiktokcringe isn't about anything cringy.

    Fph was originally about the broken logic used. Not about hating fat people. Not to say it didn't turn into that and the misnomer sub name surely didn't help.

  • Five 9's of "up" time

  • Option 3, user bans.

    196 is also spam but we're not banning that.

  • Just like how r/fph wasn't originally about hating on obese but really pointing out the flaws in logic they use to justify over eating. But we all know what it turned to which got it banned. I'm not sure it was ever as bad as the admins claimed...I think it was more to set an example.

  • I'm using liftoff till sync comes around. The experience has been pretty good coming from jerboa

  • Posts and comments is one thing... It's inherently public. But I think being able to see up and down vote publically is a tough pill. If you don't realize your votes can be seen you risk your vote being held against you. If you do know it disincentivizes you to use the vote system to protect yourself from something that should be rather benign.

  • The iptables one has me triggered.

  • What? We have other internet exchanges and who cares who owns the building? The exchange is not owned by the building owner.

  • Did you report the app?

  • I take "federated email" to refer to a juxtaposition with normal email implementation which harkens back to how it was in the 90s or early 00s where you didn't need to be registered on many SMTP servers in order to use it and it's stripped of server-side validation. There's some discussion on this topic in the fediverse.

    You're right that the default current implementation is already federated.

  • Your own email server requires near 100% uptime or you risk not receiving critical emails. If a remote email server is trying to contact your email server and it can't it's only going to retry a few times and then give up. Hosting this yourself sounds great until you realize high uptime is not cheap and requires constant attention.

    Setting it up securely can be difficult depending on your understanding of server infrastructure as well as protocols like DNS. You need to set up SPF, DKIM, DMARC, etc in order to prevent someone from faking an email from your server.

    Of course, federated email does not use SPF/DKIM/DMARC because the whole point is that someone from another server could use your server to send an email (hence the federation). Open email servers were common 20 years ago but very rare today. That makes setup easier, but the main caveat is that most known non-federated email servers will reject email from servers that don't have SPF/DKIM/DMARC because they generally end up being havens for bots and spam since there is no verification or authenticity of the sender.

    As someone who self hosts a lot of things, I would never self host my email. If i did I would be paying for two boxes in different parts of the world on different ISPs to provide that uptime. I would definitely set it up securely and not as a federated server otherwise it would be practically unusable for day to day emails.