shim__

Yes 32 bit is enough because in PAKE its used for authenticstion not encryption. Which means you get exactly one attempt to brute force after which the procedere will fail

The transfer is end2end encrypted using a PAKE key change which is aithenticated using the 3 words you enter in the reveiving end

Could have saved 50% with 'base64 -d | gzip -d'

The virtual PayPal Card works on GrapheOS

That's the neat part, it doesn't

Could have just kept using OSCP stapling

Gitlab CI is leagues better

Not even close, that's still imperative package management

Encryption does not make bit flips obivous, authenticated encryption would.

No "Find My Device" support.

I don't have any issues with it

That's why I build project specific images in CI to be used in CI. Running apt-get every single time takes too damn long.

lvm

I'd contribute to free us from JavaScript

I'm using an HDD with SSD cache for /home all non stale will be cached by the SSD

PayPal might be a bank but maybe PayPal accounts aren't bank accounts

You might still want an mediator, sure I can pay you directly on chain but what if you don't even ship my goods? I'm not going to court over an 5$ item but I don't mind engaging PayPal support.

Shouldn't be an issue to deliver two certificates an short lived one for TLS, an long lived one for the identity

Pointers are always integers, which can be interpreted as pointers.

Bad documentation is customary when writing Python

Whats the difference between Intels and AMDs approach?

I always make sure to provide an Jitsi room when inviting external people to an meeting to make sure they don't have an excuse to send me an teams link.

Sounds like electron but for cli

Swift seems more like an Go or Python alternative

Build Systems for C(++) are a mess, no package manager often means git submodules. Whereas Rust is actually easy, just requiring an `cargo install`. Don't know about Zig though Zig hasn't really taken of just yet imo.

5$/mo is expensive for a small tool. 20$ once would be fine.

You can but the server can require an device attestation during registration, proving that you're actually using an Yubikey or whatever. That isn't possible with TOTP

Sounds like an good reason to turn down invites with an Teams link

The web Server is the reverse proxy allowing the upstream to be plain http

So the image is uploaded for each recipient with an individual key?

An API call to verify an signature which could easily be verified locally?