• 0 Posts
  • 73 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle




  • Nate@programming.devtoLinux@lemmy.mlLinux and being speedy
    link
    fedilink
    English
    arrow-up
    7
    ·
    2 months ago

    This is just a theory, I don’t have knowledge of the inner-workings of either Linux or Windows (beyond the basics). While Microsoft has been packing tons of telemetry in their OS since Windows 10, I think they fucked up the I/O stack somewhere along the way. Windows used to run well enough on HDDs, but can barely boot now.

    This is most easily highlighted by using a disk drive. I was trying to read a DVD a while ago and noticed my whole system was locked up on a very modern system. Just having the drive plugged in would prevent windows from opening anything if already on, or getting past the spinner on boot.

    The same wasn’t observed on Linux. It took a bit to mount the DVD, but at no point did it lock up my system until it was removed. I used to use CDs and DVDs all the time on XP and 7 without this happening, so I only can suspect that they messed up something with I/O and has gone unnoticed because of their willingness to ignore the issues with the belief they’re being caused by telemetry




  • The CVE has to do with the utility not correctly identifying private IP addresses supplied to it in a non-standard format, such as hexadecimal. This would cause the ‘node-ip’ utility to treat a private IP address (in hex format) such as " 0x7F.1…" (which represents 127.1…) as public.

    This is a ridiculous expectation. Providing addresses in an unsupported format doesn’t yield correct results? Who wouldda thunk it. Clean up your fucking code and pass it in as expected, or make your own damn node-ip.













  • Nate@programming.devtoPeople Twitter@sh.itjust.worksRigged!
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    5 months ago

    Mythbusters: Driving Drunk Vs Mobile Phone

    Edit: Episode Part 1/3 Part 3/3 (I couldn’t find 2/3 anywhere annoyingly enough)

    TL:DW: They found driving while using a cell phone is potentially as dangerous as driving drunk. They scored lower in their crash course while on the phone

    Important to note:

    • They didn’t mention how much alcohol was consumed (or they did in the episode and not in this clip, give me a break I found this in 2 minutes on the shitter)
    • They show them taking a breathalyzer test. Im going to assume they were testing to be over the limit to get a DUI (.08% in the US), though it’s not shown or mentioned A clip of part 3/3 says that they stayed below the legal limit (@ .065%) so they would NOT be legally intoxicated
    • The sample size is like, 2. Not very statistically accurate, as mythbusters is entertainment and not a real scientific study
    • Theyre on a closed course. No pedestrians, no stop lights, no other drivers, no “unpredictable” variables in which you would need your reaction time, which would be impaired if you were drunk
    • Theyre using flip phones held up to their ears, on a phone call. Results probably vary (though are probably worse) texting vs a phone call and on modern devices vs old ones

    No real claim either way to one being worse. Moral of the story being get off your fucking phone and don’t drive drunk and you dont need to worry. [email protected]’s claims aren’t necessary wrong, but they’re not necessary right either