It’s great as it is included by default in RHEL/Fedora

type out: https://thisislegitparkingpaymentwebsite.com

Is this goatse or is it the real payment website for your parking? You won’t know unless you go there

sysctl -w vm.overcommit_memory=2 sysctl -w vm.overcommit_ratio=50

It is probably a bad idea to do that though as it will limit the amount of virtual address space an application can use

eg: https://josecastillolema.github.io/podman-wasm-libkrun/#libk...

    from subprocess import run
    from sys import argv

    source = argv[1]
    destination = argv[2]

    run([
      "rsync",
      "-zavp",
      source,
      destination
    ])

    #!/usr/bin/env bash

    source="$1"
    destination="$2"

    rsync \
      -zavp \
      "$source" \
      "$destination"

1. Lose money burning tokens in all of this stuff. 2. Lose reputation when some malware eventually makes it through

Not true. The original concept was always for them to be cloud synced.

This has nothing to do with their anti-phishing capabilities. The anti-phishing capabilities come from the fact that the password manager authenticates the application before handing out the passkey. It doesn’t matter if they are synced across devices or not.

You are correct that other login methods might be weaker than passkeys. I’m not sure how that’s related to passkeys though. In real security sensitive applications the recovery process is “go to the bank’s branch and show them your driver’s license”.

> Your master password to your cloud PW manager's vault is also phishable

No, it’s not. You would need to steal my yubikey to get access.

Like maybe if the bill amounts increase by like 10M% there should be someone that looks into it

why does this happen to you?

I mean I agree with you just that the popular perception of that word has changed