Ineentho

I'm curious on how you'd configure this. Is it common (and safe) to let a cdn cache private data for authenticated users?

Say Jira used electric, would you be able to put all tickets for a project behind a cdn cache key? You'd need a cdn that is able to run auth logic such as verifying a jwt to ensure you don't leak data to unauthorized users, right?

Couldn't even that be abused? A link that's just a square character styled either black or white could look really similar to the demo.

Usually refreshing a couple of times works for me (even just waiting a few seconds between each attempt)

If process substitution doesn't work, shouldn't /dev/stdin work? I haven't tried it, but as long as b2 doesn't try to check the file size before uploading I don't see why it wouldn't work: b2 upload_file bucket /dev/stdin < file

I think the common way is to upload your public SSH key to ~/.ssh/authorized_keys and adding a host entry to ~/.SSH/config specifying the user