• 3 Posts
  • 274 Comments
Joined 4 months ago
cake
Cake day: November 27th, 2024

help-circle











  • Yes, we’ve had outages in DCs. They are usually just a blip, because we have more than one.

    And we don’t pay broadcom anything. We migrated off of esx a long time ago.

    And the skills needed? We use a floss stack, so you need to know stuff like nginx, puppet, mariadb, and php.

    Not exactly cutting edge stuff there.

    Operations engineers make sure the infrastructure is up, and ready for code. Devs own the code.

    So, no, it’s really not all that niche.

    And I guess we need longer than 20 years to see if it works well?


  • Was it written on the phone of the people they called?

    No, but if they weren’t informed, frankly, that’s on the SM for not doing so. And honestly, anyone taking a call from a deployed soldier should just understand that reality.

    The claim was that with calls from foreign countries, if it was an American they spoke to, it would not be monitored. Only foreigners were.

    I’m not going to speak to generalities of whose calls were monitored and shouldn’t have been. Solely the item of “Americans stationed in Iraq were monitored”, which is, frankly, obviously happening. And every SM was informed as such. And they were instructed to inform their families of that fact.

    Every military spouse knew that, if they went to the pre-deployment briefings they were invited to. Every SM knew it. Every contractor knew it, and their families should have also been informed by the contractor.

    Hell, even in my state, only one party legally has to know it’s being monitored and/or recorded to be legal.




  • So for organizations that never embraced the cloud alternatives have had to maintain their own infrastructure or use commodity solutions, as you mentioned, to deliver their IT needs. How much more was spent using a general purpose approach with higher portability to deliver the same result vs a cloud providers proprietary version? Then include the time component.

    So far, speaking from experience, we saved loads of money DIY’ing it, even when deploying to the cloud, and we saved loads of time, in the long run.

    WE KNOW where the perf problem is. WE KNOW the cadence for how long a fix will take. WE KNOW the OS we’re deploying. WE KNOW the apps we’re deploying. WE KNOW how to squeak additional perf from the infrastructure, tuned to OUR NEEDS.

    If you hire talented workers, you save money and time, by DIYing the approach, as long as it’s done in a sane, and controlled manner.


  • Unfortunately, you can’t really do DNS in a decentralized manner as the concept is based on a hirarchy.

    You very much can! As long as you understand that every . is a new level of hierarchy. And that hierarchy can be arranged, in any manner one desires. You can even have a different . as the root.

    For example, you can be THE ROOT for all .stoy domains. You just have to get others to honor that, and ask you for addresses of anything in .stoy’s inventory. Of course, they can all tell you to piss off, and instead trust someone else is the true owner of .stoy.

    And, honestly? Nothing at all is wrong with that!

    What is wrong is right now, EVERYONE agrees that a handful of never-changing owners of .com, .org, .net domains (And other TLDs) is THE ONE TRUE ANSWER FOR US ALL. I didn’t agree to that. Did you? Do you enjoy Verisign being the one true keeper of .com?