• 21 Posts
Joined 5 months ago
Cake day: February 10th, 2024


  • Using a tool like this to hide sections of code presented for review places a lot of trust in the automation. If Mallory were to discover a blind spot in the semantic diff logic, she could slip in a small change for eventual use in an exploit, and it would never be seen by another human.

    For example, consider this part of the exploit used in the recent xz backdoor. In case you don’t see the problem, here’s the fix.

    Rather than hiding code from review, if a tool figured out a way to use semantic understanding to highlight code that might be overlooked by a human (and should therefore be reviewed more carefully), it could conceivably help find such things.

  • Also, when building services that are expected to send HTML email, make sure to generate a plain text version of the content and put it in the appropriate multipart section of the message. Otherwise, people reading in plain text won’t see it unless they’re willing to jump through hoops to do so (and there’s a good chance they’ll toss it in the trash instead).

    Bonus points if the plain text part is formatted well.

  • 70/30% of the logs, not of the errors. It’s equivalent to what you’re thinking of as market share. (I can’t really blame you for misunderstanding, though; this article is poorly written.)

    The proportion of errors is better explained in another article:

    In fact, for one particular type of error (decompression, a commonly performed operation in games), there was a total of 1,584 that occurred in the databases Level1Techs sifted through, and an alarming 1,431 of those happened with a 13900K or 14900K. Yes – that’s 90% of those decompression errors hitting just two specific CPUs.

    As for other processors, the third most prevalent was an old Intel Core i7 9750H (Coffee Lake laptop CPU) – which had a grand total of 11 instances. All AMD processors in total had just 4 occurrences of decompression errors in these game databases.

    In case you were thinking that AMD chips might be really underrepresented here, hence that very low figure, well, they’re not – 30% of the CPUs in the database were from Team Red.

  • I find this to either be a lie or self inflicted.

    “I’ve never experienced what you describe, so it must be either imagined or your own fault.”

    I’ve seen this nonsense over and over again in communities of all kinds, most often in tech forums (where there are always a few participants suffering from a big-fish-little-pond effect). It’s a very rude and foolish bit of human behavior.

    There are more things in heaven and earth, Horatio, than are dreamt of in your philosophy.

  • Linux user here. I don’t know of an open desktop calendar app that supports the protocol I need (CalDAV) without being one or more of:

    • Bloated
    • Too simplistic to be useful
    • Too annoying to use (poor UI)

    The best compromise I’ve found so far is Thunderbird. It is bloated, but less so than any Electron app I’ve used. I find the UI annoying, but tolerable for lack of a better option. I’m thankful for an open, cross-platform tool that gets the job done, but I wish I had one that was lightweight and pleasant to use.

    It would be nice to see some new work in this area. It’s a similar situation with email apps.

  • That explanation is fair enough but the headline is red meat the the EV disinformation brigade.

    It’s funny how words affect people differently.

    Not long ago, I posted a short, precisely-stated comment mentioning an observed fact that I had verified with a relevant authority. When I later checked in, I was surprised to find someone accusing me of spreading misinformation, and my comment removed by a moderator. It was clear that my accuser had badly misinterpreted my words. He refused to admit it or accept clarification. (And the mod had already acted, rashly.)

    I re-checked what I had written about twenty times over the course of the day. There was nothing there to support the accusation. My best guess is that my phrasing or the subject matter might have touched on rough emotions from a bad experience, leading him to see what he expected to see instead of what I wrote, and triggering attack mode.

    Communicating well really is complicated. It takes work on both sides, and can quickly turn into a bad time if it goes off the rails.

    Because of this, I’ve been making an effort to read (and re-read) charitably, especially with people I don’t know well.

  • I hate the formatting of most forums. Reddit and Lemmy’s comment nesting is excellent.

    The funny thing about this is that it’s just plain old threading, which has been around since the 1980s or earlier, with the slight variation of showing message contents directly in the thread tree instead of beside it (thanks to today’s high-res displays).

    Usenet readers did threading. Email apps could do it if the developers wanted to; the required information is there. I’ll bet there’s forum software that can do it if an admin enables it.

    For some reason, most corporations seem to have decided that classic message threading has no place in their interfaces. They resort to piling things into stacks or serializing them into seemingly endless scrolls. It fails to represent the structure of group discussions, and sadly, has been going on for so long that many people might not have ever seen the better alternative outside of reddit.