• 2 Posts
  • 59 Comments
Joined 1 month ago
cake
Cake day: November 12th, 2024

help-circle





  • Oh no, you’re getting it wrong.
    I only found the person responsible for giving me the feeling of helplessness and made them helpless.

    The other people’s lives?
    Well, I just pulled of the lever, so now nobody has the opportunity to make that choice, hence no dilemma. And who got run over in the end, I didn’t check. I didn’t know whether or not the direction got changed when I was breaking off the lever. Also, I didn’t really stop the train either, so I only stopped the dilemma from happening. I didn’t save any ppl.






  • I’m guessing the ransomware gangs would be giving better payments than regular companies asking for pen-testing.

    But with this, comes other concerns:

    • Will the pen-tester be enticed to use the “authorised hacking” as an opportunity to install a backdoor of their own or do they maintain strict borders between both jobs?
      • I’m thinking, not so much, as, if they’re already doing something illegal, they might as well just go the extra mile.
    • At the same time, pen-testers working for one company might also be used for industrial espionage efforts, by competitors



  • Did you not know?
    You can simply select all files you want to commit, in the File Manager, Ctrl+C, then paste in the terminal and it will automatically add all those file names (full paths) separated with spaces at the cursor. At least in KDE: Dolphin -> zsh + Konsole it does.

    And sure, it might look like 2 extra steps, but you will still be clicking around a lot in case of a GUI anyway.

    I tend to just type partial filenames and use tab completions, which are also pretty configurable. And the only dissatisfaction I have rn, is that I don’t have zsh module for completions with pascal case and snake case.


  • That’s definitely how it is seen.
    If I were to see “Discard Changes” anywhere in a dialogue, I would assume it will discard whatever changes I made in that dialogue. In this case, probably some source control related changes. If it were to say “Warning: This will Discard ALL changes!!!”, I might do a double take, but had I never used git CLI before, I would still assume that at most it would discard “ALL” changes made in the current session.

    For me personally, I would consider it more useful for it to say:

    This action will delete the following files:
    - followed
    - by
    - a
    - list
    - of
    - files
    - that
    - would
    - be
    - deleted
    Continue?
    

    Which neither has to look like a warning, acting like you might be doing something you don’t want to and also is much more useful for someone like me who wants to double check what exactly I am deleting.


    Also, I have used git CLI before and apart from being able to see blame in the editor itself and maybe a better representation of tree, I don’t feel the need to use any git GUI tool. Even when I tried, I realised it was slower and more finicky to use. So, it would stand to reason that it should be targetted towards people who don’t use CLI (and might have never used git CLI).