We’re probably getting URI encoding for free with the native JS API that constructs the URL

Though I'm not sure who's in the wrong here. I'll investigate some more.

hampus

Perhaps we're double encoding when we shouldn't be?

Yes, as far as I can tell, it seems to be double-encoded when it shouldn't be.

// stacker.news
decodeURIComponent(decodeURIComponent("%257B%2522identifier%2522%253A%2522SatsAllDay%2540stacker.news%2522%257D"));
'{"identifier":"SatsAllDay@stacker.news"}'

// blixt wallet
decodeURIComponent("%7B%22name%22%3A%22Hampus%22%2C%22identifier%22%3A%22hampus%40blixtwallet.com%22%7D");
'{"name":"Hampus","identifier":"hampus@blixtwallet.com"}'

SN release: nostr crossposting, symmetric lud18, quote replies, @ autocompletes

k00b

> Perhaps we're double encoding when we shouldn't be?

Yes, as far as I can tell, it seems to be double-encoded when it shouldn't be.

A quick look.
Yours require two `decodeURIComponent`s:

```
// stacker.news
decodeURIComponent(decodeURIComponent("%257B%2522identifier%2522%253A%2522SatsAllDay%2540stacker.news%2522%257D"));
'{"identifier":"SatsAllDay@stacker.news"}'

// blixt wallet
decodeURIComponent("%7B%22name%22%3A%22Hampus%22%2C%22identifier%22%3A%22hampus%40blixtwallet.com%22%7D");
'{"name":"Hampus","identifier":"hampus@blixtwallet.com"}'
```