you thinking like a download_hash tag or something?
our download_url values actually already include a hash - that’s how we identify files, by their content hash. but ultimately we want the media api to be user configurable so I think this makes sense.
Or just an `x` tag with the hash as the NIP_94 does
Also, which relays do you have your content on? I can barely find it.
x sounds good to me.
1808s are only sent to relay.stemstr.app at this time. now that other clients are consuming them we need to start broadcasting further. there’s already a design for “share to my relays” - nostr:npub1xv6axulxcx6mce5mfvfzpsy89r4gee3zuknulm45cqqpmyw7680q5pxea6 keep me honest here
