Should be stripped in the client

I expect it to be removed at every step.

I prefer it as a client setting

Real answer from having built this recently: it can't reasonably be the server's job. Blossom is content-addressed by SHA-256 (BUD-11 auth is literally scoped to the file's own hash) — if the server stripped EXIF, the served bytes would differ from what got hashed/authorized, breaking that whole m...

nostr:nprofile1qqsp5h8l2yvdqudzch2x2drn82ae70wdl3qmyndszvhuyrdlq8r477qf8xlvn client side, and before the hash. once a file with gps in it is up, blossom keeps that blob at its own address forever, so stripping it later just creates a second file and the original is still sitting there.