• 1 Post
  • 259 Comments
Joined il y a 1 an
cake
Cake day: 19 juin 2023

help-circle




  • I’m gonna go with no, because of containerization and permission management. On your computer, any program can do pretty much anything, unless you explicitly take measures against this. On a smartphone, you get a lot of control over your apps. In newer Android versions you can even completely disable cameras and microphones (even if only in software).

    I would use a throwaway account and avoid giving Google any personal data tho. Of course they could still figure stuff out, but it’s harder and unreliable, not to mention super-duper illegal (at least in the EU), so I kinda doubt they go the extra mile.






  • Tons of people making Python comparisons regarding indentation here. I disagree. If you make an indentation error in Python, you will usually notice it right away. On the one hand because the logic is off or you’re referencing stuff that’s not in scope, on the other because if you are a sane person, you use a formatter and a linter when writing code.

    The places you can make these error are also very limited. At most at the very beginning and very end of a block. I can remember a single indentation error I only caught during debugging and that’s it. 99% of the time your linter will catch them.

    YAML is much worse in that regard, because you are not programming, you are structuring data. There is a high chance nothing will immediately go wrong. Items have default values, high-level languages might hide mistakes, badly trained programmers might be quick to cast stuff and don’t question it, and most of the time tools can’t help you either, because they cannot know you meant to create a different structure.

    That said, while I much prefer TOML for being significantly simpler, I can’t say YAML doesn’t get the job done. It’s also very readable as long as you don’t go crazy with nesting. What’s annoying about it is the amount of very subtle mistakes it allows you to make. I get super anxious when writing YAML.








  • UnfortunateShort@lemmy.worldtoMemes@lemmy.mlRule
    link
    fedilink
    arrow-up
    7
    ·
    il y a 1 mois

    Make a habit of reading takes (from reputable / serious sources) that you think you’ll disagree with.

    Even if it doesn’t change your mind, you will understand other people’s POV. This is very important for understanding your own stance better and finding flaws and uncertainties in it.

    It also tends to humanise “the other side” (whoever that is for you), which makes it easier to have a constructive argument rather than meaningless fights.





  • I’m just gonna go ahead and say it: 16 Characters are sufficient and 20 pretty damn secure.

    That is assuming they do stuff right and there are no vulnerabilities, which they won’t and there are. However they may manifest, they are a greater concern at 16+ characters, especially if they don’t offer 2FA.

    The reason is that even if machines become powerful enough that 16 characters can be bruteforced, which they can’t atm, you can effectively defend everything against bruteforce attacks by other means. Including but not limited to limiting login attempts, salts and pepper, multiple encryption layers etc.

    With just a salt pepper you can make a 16 char password effectively a 24 char password… Or a 2.000.000 char password. Assuming it is not stolen alongside that is.

    Edit: Changed ‘salt’ to ‘pepper’.