Good point. It’s just how to publish the info once we have it. Who signs the event. Which key should the client trust for this info. It is not generated synchronously, and HTTP has a HEAD method that is cheaper than relay queries
Publish it with a key owned by the nostr.build service specifically for these matters and tell clients what that key is so they can trust it.
I’ll propose a PR to add trusted npub in the nip96 JSON. Probably a list of them, to allow rotation, etc
Anarchist Meditation2 #test2 https://image.nostr.build/bf91c069611c97ad8983c1aeed444e8bc16ee5293416c6b50a444317608765a1.jpg