Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)CO
Posts
0
Comments
375
Joined
5 yr. ago

  • I wonder if anyone is doing large scale searches for source releases that differ in meaningful ways from their corresponding public repos.

    It's probably tough due to autotools and that sort of thing.

  • All of this would be avoided if Debian downloaded from GitHub's distributions of the source code, albeit unsigned.

    In that case they would have just put it in the repo, and I'm not convinced anyone would have caught it. They may have obfuscated it slightly more.

    It's totally reasonable to trust a tarball signed by the maintainer, but there probably needs to be more scrutiny when a package changes hands like this one did.

  • it had a way to know it was being emissions tested and so it adapted to that.

    Not sure why you got downvoted. This is a good analogy. It does a lot of checks to try to disable itself in testing environments. For example, setting TERM will turn it off.

  • GrapheneOS + Pixel phone is the only true option if you want any kind of ensure that even of the device is lost your data won't be accessed.

    I think that's an exaggeration. You don't need secure boot for your data to be encrypted. What secure boot prevents is someone modifying the device without your knowledge (e.g. to capture your keys).

  • There's a couple of ways I could imagine debugging this.

    One would be to disassemble MapEngine.MapsContainer.IsExists and see why it would throw that exception. It's quite strange because it should act like it's running on windows.

    The other would be to enable WINEDBG stuff or possibly use strace to figure out what it did before throwing that exception.

    Have you tried 32-bit wine?

  • This is me too, but I just switched to alacritty from urxvt (due to some new bug with control characters).

    I prefer my terminal to purely show text, and I use tmux for all the fancy stuff.

  • Hmm, nothing there looks like an index display. My vive looks like:

     
        
    DisplayPort-1 disconnected (normal left inverted right x axis y axis)
       2160x1200     89.53 +
       1920x1200     89.53
       1920x1080     89.53
       1600x1200     89.53
       1680x1050     89.53
       1280x1024     89.53
       1440x900      89.53
       1280x800      89.53
       1280x720      89.53
       1024x768      89.53
       800x600       89.53
       720x480       60.00    59.94
       640x480       60.00    59.94
    
      

    Perhaps there's a good reason for that, but this seems like a dead-end.

  • According to the Journal, plaintiff attorneys usually get one-third of a verdict or settlement amount.

    This isn't a an amount awarded in a verdict though, is it?

    Plaintiff's Counsel have not been paid for their work, nor have any of their costs or expenses been reimbursed, and litigating this Action required the allocation of a substantial amount of Plaintiff's Counsel's time and resources over six years, including considerable out-of-pocket expenses,

    So that's roughly 100 lawyers working full time for 6 years at $5k per hour. Seems legit.

    In any case this is hilarious and exactly the kind of thing Elon would try.

  • It should show up in the output of xrandr. At least my Vive does. Could you share that?

    I believe in the past I was able to turn the display on with xrandr and extend the desktop to it. That would at least prove that the hardware works.

  • I feel like node's async model makes it really easy to cause a bug like this, and really difficult to track it down.

    It was left to the OS to catch the leak, because the program was written in such a way that it was able to run a gazillion of these tasks concurrently.