Oddbean new post about login | logout The creation of the world: nfile1qpqxzvmzvfnr2efkvgukyerp8p3nqdn98qunxcm9x4nrjdnpvyuryv3hv5cxzvmrxsmnsvmrv9nrycenxp3ngdmzxpjrscf3vdjkyerrvvqks6r5w3c8xw309ahx7um5wf3ksetrdvhx6ef0d4jkg6tp9ac82cnvd93j7cfnvf3xvdt9xe3rjcnyvyuxxvpkv5urjvmrv56kvwfkv9snsv3jxajnqcfnvv6rwwpnvdskvvnrxvcxxdphvgcxgwrpx93k2cnyvd3juam9vfcqz8ngw368que69uhkjtnwdaehgu3wvf6kjmry9agrsepc9e48qecsh4uft
I assume Amethyst just isnt yet compatible?
Probably needs a nostr: prefix
What is this?
It decodes to {ox, urls}. The idea is that using NIP 96 people can upload the same image to multiple hosting providers, pass around an nfile, and if one of the hosts deletes the image there is an alternate url embedded in the note that clients can fall back to. What do you think? how many URLs can it hold?
We really should standardize on a solution for this. I actually was just working on something similar, an embeddable `nfile` entity. This fails the naive fallback test, but I don't like that nip 54 prioritizes one url in particular. This way we don't need a full event too, just a data structure that can add blurhash etc as needed. nostr:nevent1qqswc3dr5zwqh6dn9m5pgruy90y40atd9dl4q8ajy8rckmhun7g9u5spz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9rhwden5te0wfjkcctev93xcefwdaexwtcpzdmhxue69uhk7enxvd5xz6tw9ec82c30qyvhwumn8ghj7un9d3shjtnndehhyapwwdhkx6tpdshsz8rhwden5te0vf6kx6m9wshxxmmjv93kcefwwdhkx6tpdshszrnhwden5te0dehhxtnvdakz7qgnwaehxw309ac82unsd3jhqct89ejhxtcpr3mhxue69uhkx6rjd9ehgurfd3kzumn0wd68yvfwvdhk6tcpzemhxue69uhhyetvv9ujumt0wd68ytnsw43z7qgjwaehxw309ac82unsd3jhqct89ejhxwvcy34
