• 5 Posts
  • 696 Comments
Joined 5 years ago
cake
Cake day: January 21st, 2021

help-circle



  • The fact is that it depends and it is a bit confusing for people not familiar. But it isn’t hard to get used to.

    +8Q, Paris isn’t specific enough. There are multiple +8Q inside Paris. It can also be a bit risky to make short codes like this especially with larger cities as different maps may put the city in different spots.

    What does work is +8Q Eiffel Tower which is useful for something like “Meet me here by the Eiffel Tower” or “I’m right here” when you are texting someone you are meeting and you know you are close but can’t see each other.

    So you end up with a few common options:

    • +8Q Eiffel Tower We are pretty close together but need to get the exact spot.
    • V75V+8Q Paris, France For exact spots around a known area.
    • 8FW4V75V+8Q For fully qualified with no reference needed.

    And a few less useful options:

    • 8FW4V7+ This large part of a city.
    • 8FW4+ This part of the country.
    • 8F+ This area of the world.

    If I was designing the system I don’t think I would have done this “trailing zeros assumed” approach. Because IMHO for day-to-day use V75V+ Would be more useful as a shortcut for ????V75V+ rather than the actual V75V????+ showing a rough location on a human scale (in this case the Eiffel Tower park is pretty clearly targeted) rather than an area larger than a city. But that is really the only complaint I have.






  • kevincox@lemmy.mltoPrivacy@lemmy.mlPasskeys
    link
    fedilink
    arrow-up
    0
    ·
    6 days ago

    There are a few main benefits.

    1. For hardware-backed keys they can’t be stolen aside from physically stealing the hardware. So unless your machine has malware there is no way for an attacker to authenticate using them.
    2. Even for software keys the site you authenticate to doesn’t learn enough to impersonate you. For example if for some reason your bank leaked some logs with PW + MFA someone could use that to log in as you (although admittedly short timeouts on MFA validity makes that window very small).
    3. The browser ensures that you only authenticate to the correct domain. So it prevents phishing. (Although a password manager that only fills into the correct domain also accomplishes this.)

    So I think if you are using unique passwords with an automated password manager the effective benefit is quite small. However for the “average computer user” who likely has less than 5 passwords that they use for everything it forces a pretty high base level of security.






  • You seem to be making this very complex. But it really isn’t. Yes, git doesn’t track renames. So you are working around it by splitting your operation into 2 commits.

    1. A pure rename.
    2. A file change.

    This way 1 is always considered a rename and 2 is just a regular file change with the same path. You may also consider tweaking the default rename detection threshold with flags like --find-renames or options like diff.renameLimit.

    Would it be nice if Git tracked renames? Probably. But that isn’t how the data model works so it is unlikely to happen soon. But maybe they could add some metadata.



  • Of course, but because the law is so protective you won’t need to 99.9% of the time. Canada also isn’t a very litigious place and even if it does get raised it will probably get thrown out quickly. To most doctors it is also a huge stressors to watch someone that they can help die. So overall the balance is well worth trying to help out.