yes the # borks it. fixed in incoming update.
ahem... well my first nostr ln invoice... still very special
hahaha. also having nice rendering of ln invoices in astral is hopefully coming soon!
so kind... here you go...
lnbc200u1p36pmglpp5hahku5u8plmq6k30naztm5l28w8kqc9zfpedgn2wzxt8k6ttuxhqdqqcqzpgxqyz5vqsp58z95jgaxeshsw3t37vq56h7kje6cqetn02l3rdeney0ejcf70mgq9qyyssqefduc97uzstjmw6wj0z4qwalz98cd9hx2hre4g2t4yu9ns79vs0r75j22u3rm3uqknrf864j7cxdtjhytjknel0d0r8demw33pug42qpy460k0
wow thank you false faucet... this my first ln invoice too! hopefully it works..
lnbc200u1p36p64qpp5dhl9mlyvr7khkm7ye4jff6qhcgcn5n9hh7n7f7cpzlfdakn3vcnqdqqcqzpgxqyz5vqsp5lj8ydhrx7wwht88vz4xt0wq3w2vmnms4qumv73mxvj0n7v7g43hq9qyyssqh9jrz5tg3shyaf4hum9lrfqg09x6pqu9htg934zr5ls6jxft5hy3mqg2lxqrzc76qzad3hhhay249m73fcd2hy4jafev6dpppzq2f7sq4hz44e
no this is a bug I've been meaning to get to. its caused by 2 different fetches for messages (already seen and new) and somehow the permission pop up doesn't handle all messages. if you refresh the page all the content should populate.
yes, unfortunately. however for nip05 its in the spec that it should be served with cors headers.
one hack that #[5] thought of was just putting it in your githubΒ πΒ #[6]
Not sure what client you are on but there are some problems with loading images on some clients because of CORS issues (https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS). Astral has this problem I think, isn't that correct #[2] ?
yep this is known issue. trying to find time to figure out how to stand up a proxy to fix this ππ
astral has always shown avatars served with cors headers. the ones without are still broken, no proxy yet
too early for that. but fiatjaf's expensive relay only allows paid users to post. semisol has a relay that only allows approved pubkeys. so we have some rudimentary stuff but nothiing like twitter or fb moderation.
do you know of tools to parse these and display them as qr codes in web apps?

