localsend VS protocol

I agree and get your point.

But localsend has worked well for me. Yes, it requires an app but if we could get vendors to bundle that rather than a boatload of bloatware.

I know that it would be to optimistic to hope for Google.

See https://localsend.org/

Spread the word.

https://github.com/localsend/localsend

Something to consider, although I'm not sure how much it practically matters.

It works like a charm, and is really easy to use

https://github.com/localsend/localsend

Use local send to send files and folders.

I've recently discovered and can recommend LocalSend. It's FOSS, cross-platform, and it just works. Github page with more details here

Edit: This is very simple implementation, even a POC, for personal use between our own devices at home or other personal private network. Even works on hotspot. But no HTTPS, so don's use on non-private networks. LocalSend, as suggested by u/Fede777 seems to be better for every other use.

Not the fort-knox implementation it claims on the tin.

'LocalSend uses a secure communication protocol that allows devices to communicate with each other using a REST API. All data is sent securely over HTTPS, and the TLS/SSL certificate is generated on the fly on each device, ensuring maximum security.'

How do they achieve maximum security while generating X.509 certs on device?

Let's look; 'https://github.com/localsend/protocol#2-fingerprint'

'When encryption is on (HTTPS), then the fingerprint is the SHA-256 hash of the certificate'

Confusingly there is a HTTP non encrypted mode, and the docs claim the fingerprint only used to avoid discovery collisions.

Out-of-band [visual comparison / QR code scanning step] sharing of fingerprints COULD be acceptable to prevent 'man in the middle' attacks, however the documentation doesn't seem to indicate that this detail is surfaced or shared with the user.