My username is a wordplay on the Linux command filesystem check: fsck.

  • 1 Post
  • 417 Comments
Joined 1 year ago
cake
Cake day: February 24th, 2024

help-circle





  • What registrar was that? Were they as big as Cloudflare? How exactly did they “go tits up”? Isn’t the situation you describe a completely different scope from an individual’s usecase? It’s also an anecdotal point of data without including the full context of how common that situation is. “It happened to me once, and I have heard stories” does not necessarily mean it’s common enough for everyone to prepare for every time. I’ll remain skeptical of the

    Mainly, though, I’m not saying it’s a bad idea in total. I just think that for someone who is inexperienced with DNS management and self-hosting, those types of concerns are already unlikely and just keeping the environment simple and cost less has far more value than being prepared for unlikely scenarios. It could even prevent self-inflicted issues by keeping it simple, which would be far more likely than Cloudflare’s infrastructure creating a problem that they have to remediate themselves.

    If anything, the true argument for risk mitigation would be to have multiple DNS servers for redundancy.

    I just don’t believe that, in this type of usecase, it’s worth pressing for and that there’s more of an argument to keep it simple.

    Additionally, you can leave out trying to use your credentials and a hypothetical group of people to make your argument for you. It makes it seem like you’re trying to talk down.


  • I get that you’re likely exaggerating by saying “it’s no extra work”, but managing another account is markedly extra work. It will also cost extra because Cloudflare does not add any markup for registration, which is why they are the cheapest registrar.

    I think the convenience and reduction of cost greatly outweighs the highly unlikely situation where “something goes fucky”. If it does, then what? You can’t make DNS updates for a little while?

    The most likely reason to get locked out is billing issues, or maybe you lost your login information or something like that, which is going to be the same risk regardless of who your registrar is. Otherwise you’d have to be involved in some sort of legal issue associated with your domain and that is a much deeper issue than can be solved by simply changing nameservers.



  • go $fsck yourself@lemmy.worldtoComic Strips@lemmy.world"Joe Biden's fault"
    link
    fedilink
    English
    arrow-up
    19
    arrow-down
    8
    ·
    2 days ago

    That’s not how you phrased it, though.

    If that was the point, then simply adding “as well” or “too” at the end makes that clear. Without it, it frames it as if the blame is being shifted instead.

    When someone robs your house, you blame the robbers. When the police refuse to do anything about it and you get robbed again by the same person 4 years later, you blame the police, too.






  • Yeah, I think the title is just bait to get more clicks. Leveraging legitimate fear for what Trump’s administration is doing to garner more clicks is pretty scummy.

    It’s also ironic that the premise they are playing on to write this article is anti-trump, but then they go on to list Protonmail even though the CEO has been kicking Trump’s boots.

    Edit - Oh, look at that… a referral link to Proton.

    They also use GoDaddy for their domain registrar. No one who runs a website and uses GoDaddy should be trusted to provide any reliable advice on anything tech related.

    Okay. What the fuck?

    *Again - no affiliate links. You can count on that, for every post on this blog. I don’t profit from you as a reader in any way beyond your direct support, if you so choose.

    Then what the fuck is this?

    Edit again - Apparently their site is a Ghost blog, which has a feature that adds that referral parameter automatically. It’s called “outbound link tagging”. At least it was not intentional, but it does show more evidence that this person should not be relied on for good information.



  • I’m not sure what the consequences are for ignoring it, but it would violate the ICANN RAA to lock a person out of being able to transfer their domain except for legal reasons like evidence of fraud or a court order. Sure, they can terminate your account on their services but they can’t prevent you from transferral without violating their agreement with ICANN.

    It would be a weird scenario that you’re describing that would be unusual and exceedingly rare. You would need to be directly connected to something highly illegal for that to happen, not just a normal user.