• 0 Posts
  • 74 Comments
Joined 1 year ago
cake
Cake day: August 21st, 2023

help-circle
  • Windows 2000 was a good operating system by any measure. It was rock solid, capable, well-supported, could scale from desktop to large enterprise deployments and everything in between, reasonably secure compared to their previous operating systems, etc. I never did like Microsoft operating systems, but Windows 2000 was actually good. It was a breath of fresh air at the time. We had NT 4, which was stable and reliable, but was limited by a lack of DirectX and became cumbersome in large deployments. Then we had Windows 95/98/ME, which was the garbage that crashed all the time.


  • Why? I think there’s a decent chance they don’t survive this - at least their commercial airplanes. I won’t fly on a Boeing any time soon, if ever. It will take years to get back to a safety culture and there are tons of shit planes manufactured in the past several years that will be in service for decades.

    If I was a pilot, I wouldn’t want to fly one either. They just had another incident where a pilot says the gauges went blank and he lost control. If a pilot union starts pushing back, it’s game over.

    Would you fly on one of their planes?



  • People with private jets often charter them out when they’re not using them. The best place for an airplane is in the air. Only bad things happen when you let it sit around on the ground all the time. It’s not much different than commercial planes that spend most of their time in the air.

    Sure, a private jet will have more emissions than an Airbus, but it’s a marginal increase. It’s not like rich people with their planes are producing a million times more pollution that wouldn’t exist if they didn’t have a private jet. They’re still going to fly, at least for longer trips.

    It’s easy to go down a rabbit hole with this line of reasoning. Who else is using less efficient aircraft or taking unnecessary flights? Are all those police helicopter flights necessary? What about people flying to go party on an island somewhere versus some more noble purpose? Or airlines with a half empty flight? Meanwhile, it’s the oil companies producing the vast majority of carbon emissions while we squabble over travel itineraries and choice of aircraft.



  • So help him out instead of trying to steal the project out from under him. I see there are other contributors in the kbin repository. This fork comes off as really sleazy.

    Ernest put in the work and established a community. Now somebody comes along and tries to move that community over to a fork. That’s some bullshit. Zero creativity with the name too. I wouldn’t be surprised at all if this group tries to monetize this thing if they manage to replace kbin. Community-focused my ass. If it was community-focused, you wouldn’t be on here trying to split the community.


  • Dude, just build a better product and let it speak for itself. Or maybe try contributing to kbin. It’s not cool to always be harping on the guy for his development pace and trying to pull people over to your fork. Like, we’re supposed to hop over there because you’ve made more commits this week? How do we know your project would be any better off if it ever blows up the way kbin did?

    That kbin dude got tens of thousands of subscribers overnight and then put on blast with bug reports and feature requests. He’s done a good job running the site too. He’s got a pretty good track record as far as I’m concerned. He hasn’t asked for shit in return except a little space to maintain his sanity.


  • Nobody is buying this and I don’t think they are trying very hard to sell it either. Notice that this pricing is only in the U.S. This seems like a ploy to bolster their case for damages and/or royalties in a settlement. Or maybe just part of their patent defense strategy. This company is primarily in medical tech. Even if they aren’t so interested in the consumer market, they have to protect their patent or someone in a market they do care about will get away with it too. I would assume it strengthens their case if they can demonstrate material damages in a market they participate in. So quickly unveil a prototype, price it so there’s little to no demand, don’t bother manufacturing a product nobody wants, win the case, cancel the product.













  • In all fairness, 13 days is a fairly quick turnaround for patching in the enterprise. The breach was only 6 days after disclosure. They were almost certainly in the planning stages already when this happened.

    I used to be the head of IT in a large organization that worked with clients in highly regulated sectors. They all performed regular audits of our security posture. Across the board, they expected a 30 day patch policy. For high profile vulnerabilities like this one, they would often send an alert and expected imminent action within a commercially reasonable time frame. We would get it done anywhere from 24 hours to days later depending on the situation and whether there were complications. It was usually easy for us because we were patching every device and application on the network every couple weeks anyway. A hotfix is much easier to deploy when everything is up to date already and there are no prerequisite service packs. We knew we were much faster than most and it took a lot of work to get there. Thirteen days is a little slow for a 0-day by our standards but nowhere near unreasonable.

    The reality is many enterprises don’t patch at all or don’t do it completely. They may patch servers but not workstations. They may patch the OS but not the applications. It’s common to find EOL software in critical areas. A friend of mine did some work for a railroad company that had XP machines controlling the track switches. There are typically glaring holes throughout the company when it comes to security. Most breaches go unreported.

    Look, I hate Comcast as much as anyone. They suck. But taking 13 days to patch isn’t unreasonable. Instead, people should be asking why there weren’t other security layers in place to mitigate the vulnerability.