That’s the problem. WhatsApp will use GCM for push notifications. No GSF, no GCM.
openpgp4fpr:358e81f6a54dc11eaeb0af3faa742fdc5afe2a72
That’s the problem. WhatsApp will use GCM for push notifications. No GSF, no GCM.
You don’t need to sign in and it’s not needed for their location services. It works without it. It complains but still works.
GrapheneOS supplies a sandboxed version of those libraries and the underlying location requests don’t go to Google.
You sure can.
Victoria Metrics is a timeseries database for long term storage. Can be used as a direct plugin to Prometheus et al.
Luckily I signed up with fake details (name, address, etc.).
Untrue. I work for a global enterprise company that transacts hundreds of millions of dollars via LE certs.
mautrix-whatsapp and, yes, self-hosted.
I use Matrix with a WhatsApp bridge. Best of both worlds.
SELinux
The reason is “asymmetric routing”. The return ping packets are traveling a different route on the way out than on the way back.
This implies they’re storing the plaintext password.
Ideally the password would be hashed with a salt and then stored. Then it’s a fixed length field and it shouldn’t matter how long the password is.
That’s how they “win”; by making it “not worth the effort”.
From the context, children.
The execute bit on directories allows for traversal of the directory (i.e. allows you to cd
in), while the read bit allows for listing the directory contents (e.g. ls
).
“Hiring”? Is “raising” a better word?
My local Piped instance still works.
Webauthn already exists.