Haha. Nice!! That’s awesome. I wonder if you could try with the escaped unicode variant? I doubt that field is ultimately parsed as HTML (I think that particular function happens in the Netlify Core API Ruby app, not in open source GoTrue) so it’s likely the escaped character would end up as text in the subject, but hey, if you want to try it and see, I’d love to find out!
🦁
=>
⛳
=>
You could try Unicode encoding: U+1F601
Or even raw hex (but I very much doubt this will work): \xF0\x9F\x98\x81
Feature request stands
Yea, Is that on GitHub or… I’ve never done a feature request.
Ah, there isn’t a public repo where you could file that, but I have filed one for you and will let you know if it changes by posting a followup in this thread.
I do not expect it to change anytime soon since this is the first such feature request on the topic, and it feels like not-a-blocker to me (more of a nice-to-have), just to set expectations.