• 0 Posts
  • 74 Comments
Joined 1 year ago
cake
Cake day: June 30th, 2023

help-circle


  • I disagree that that warning is reasonably clear. Even the comment that included it has the line of thought, where the user, not knowing what terms git uses thinks that they just did an action that is going to change each of their files. It makes sense that they’d want to discard those changes. That user then goes on with some snark about not wanting to learn any more about what they are playing with and that other programs would do the same, but “discard changes” seems like it would have a clear meaning to someone who doesn’t know git.

    The warning says it isn’t undoable but also doesn’t clarify that the files themselves are the changes. Should probably have a special case for if someone hits discard changes on a brand new repository with no files ever checked in and hits discard on a large number of files instead of checking them in. Even a “(This deletes all of the local files!)” would make it clear enough to say what the warning is really about.



  • I’m not sure there’s any guarantee that it will ever be sorted, since bit flips will be random and are just as likely to put it more out of order than more in order. Plus if there’s any error correction going on, it can cancel out bit flips entirely until up to a certain threshold.

    Though I’m not sure if ECC (and other methods) write the corrected value back to memory or just correct the signals going to the core, so it’s possible they could still add up over time and overcome the second objection.







  • It’s like so many programmers never evolve past the “playing around with web dev stuff” days. The fact that JavaScript is one of the most used languages is appalling.

    The whole 1+1 = 11 meme made me laugh and then avoid JavaScript whenever possible, but I wonder if many others saw it and thought, “now I’ve gained more experience in JavaScript!”





  • Yeah no worries and agreed. I hate seeing commercial sites using worse password sanitization practices than I used for my first development website that wasn’t even really intended for anyone else to log in to and any max length suggests the password is either stored or processed in plaintext.

    IMO it should even be hashed on the client side before being sent so that it doesn’t show up as plaintext in any http requests or logs. Then salted and hashed again server side before being stored (or checked for login).


  • Correct, hence the sentence after the one you quoted :)

    If any service can recover your password and send it back to you rather than just resetting it for you to set a new one, don’t rely on that service for anything you want to keep secure. And certainly don’t reuse a password there, though you shouldn’t be reusing passwords anyways because who knows what they are and aren’t storing, even if they don’t offer password recovery.


  • Once upon a time, battle.net passwords weren’t case sensitive. I used upper and lower case letters in my password then one day realized I didn’t hit shift for one of the caps as I hit enter out of habit, but then it still let me in instead of asking for the password again.

    It was disappointing because it takes more work to remove case-sensitivity than to leave it. I can’t think of any good reason to remove it. At least the character limit had a technical reason behind it: having a set size for fields means your database can be more efficient. Better to use the size of a hash and not store the password in plaintext, so it’s not a good reason, but at least it’s a reason.



  • When I first heard of the MS feature, my first thought was that there’s gotta be a more efficient way to do this than taking screen shots and analyzing the image. The window manager has all of that information plus more context (like knowing that these pixels are part of a non-standard window that uses transparency to act like a non-rectangular shape, while this thing that looks like a window is actually an image because the user was looking at someone else’s screenshot).

    Even better would be integration with the applications themselves; they have even more contextual information than the window manager has.