How does blossom address media optimization and exif scrubbing?
If you choose to upload to a server that does no media optimization, isn't that killing user mobile data?
Discussion
The optimization has to happen before signing, so a separate process would need to run that before blossom is even involved. That or the client uses some sort of trusted proxy that can perform these actions in the middle.
Blossom does not have anything in the spec right now for processing blobs. although its something I've been thinking about adding.
Optimizing media and removing exif metadata is a trusted operation and isn't deterministic. so it has to be performed by either the client or a trusted server.
Ideally a user would select a specific server that they trusted to "process" their media, and return the new blob / sha256. then the user (or the server) could upload that to multiple other blossom servers for resilience
Thanks sir, was curious about this too.
Will not be easy to compete with Big Tech on that front, damn.