• 1 Post
  • 116 Comments
Joined 3 years ago
cake
Cake day: June 22nd, 2023

help-circle
  • I’ll further argue that the Paradox of Intolerance, used in this instance, implies that if we do not tolerate intolerance we can effectively snuff it out or meaningfully prevent it and thus we do not have to tolerate intolerance at all. The sad fact is that that is not true unless you are willing to cull opposing opinions

    That is exactly what is necessary, to snuff out intolerant voices as the one thing the tolerant must do. Opposing opinions is what they claim to be, but the intolerant hate spewers isn’t about opposing opinions at all, it’s rather “you are not entitled to your opinion”. It’s a false equivalency that allows intolerant to gain an advantage because they do not play by the same rules or definitions. The whole moving goalposts strategy for instance.


  • If you flipped the situation around and a radical conservative hacker in Russia hacked an LGBTQ site you would immediately call that a crime.

    Indeed I would. But that’s because it would be someone trying to silence a group and promote intolerance. The proper equivalent scenario would instead be someone making a hack that amplified and encouraged equality and tolerance……which doesn’t happen.

    I feel strongly that rules and laws should be enforced equally and that you can’t put them on a spectrum.

    Sure

    ere is another example; when Democrats were found to have potentially taken top secret files, by accident or not, the party had to investigate them with the same level of conviction as they had with Trump because failing to do so undermined their own argument.

    And therin lies the problem. The democrats may indeed investigate and prosecute their own, see Al Franken……but the other side has no intention of doing the same. So the law is already not being applied equally, and “the high ground” of tolerating intolerance simply backfires. That is exactly the paradox.




  • You’re talking high availability design. As someone else said, there’s almost always a single point of failure but there are ways to mitigate depending on the failures you want to protect against and how much tolerance you have for recovery time. instant/transparent recovery IS possible, you just have to think through your failure and recovery tree.

    proxy failures are kinda the simplest to handle if you’re assuming all the backends for storage/compute/network connectivity is out of scope. You set up two (or more) separate VMs that have the same configuration and float a virtual IP between them that your port forwards connect to. If any VM goes down, the VIP migrates to whatever VM is still up and your clients never know the difference. Look up Keepalived, that’s the standard way to do it on Linux.

    But you then start down a rabbit hole. Is your storage redundant, the networking connectivity redundant, power? All of those can be made redundant too, but it will cost you, time and likely money for hardware. It’s all doable, you just have to decide how much it’s worth for you.

    Most home labbers I suspect will just accept the 5mins it takes to reboot a VM and call it a day. Short downtime is easier handle, but there are definitely ways to make your home setup fully redundant and highly available. At least unless a meteor hits your house anyway.








  • Decipher0771@lemmy.catoSelfhosted@lemmy.worldemergency remote access
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    3
    ·
    4 months ago

    I buy better gear that doesn’t regularly require a reboot

    My mikrotik has not NEEDED a reboot ever, except when I run upgrades. Everything is set up to auto recover when disconnects happen, and power up properly if there’s an extended power failure that causes UPS shutdowns.

    I will never understand why people think rebooting their router regularly is a normal thing. That just means your gear or setup is crap.