Oddbean new post about | logout
 The above post was a test to help me develop some new gossip code that will be on master within a week or two, which I just completed. 
 You also need to consider optimizations by media services
That is pretty common 
 If a media service optimizes an image and then provides the URL, we will download the optimized image and hash that and provide that in the imeta tag, along with 'ox' for the original data pre-optimized.  The x tag should still verify.  This is work I haven't done yet (most of this last week was refactoring, not actually adding this new code).  
 Some media services do optimizations differently based off of client also. And re-optimizing images.

My personal opinion is that we also need a hash that reflects the overall content of the image roughly, and a way to signal to image services “return original optimized version” in case of things like a zoomed up view or doubt about content integrity. 
 The problem is that the current state of Nostr media makes it impossible for services to optimize without making someone mad.

Clients should signal what they need (data saving preference, rough resolution, intent such as to view up close/save or just timeline) and servers should provide that. Servers should also be able to optimize however as long as the original can be requested