I like the idea of it showing the input without too much hassle. A nitter of nostr.

The input field could be more feature reach (paste anything type) if not confusing. For example, I pasted an eventid in hex and got a syntax error.

Error handling could be more graceful and less intimidating.
https://nostrcheck.me/media/public/e45fd801ef0f8698af695ee36db3838f6f9ad6a8a4a59ea659f5d09f9426e5c9.webp 

 who or what is the input for? 

 It’s a edge case but clients offer eventids as hex and how do you get a regular event out of it? 


Some clients accept it in their search bar but others don’t.  And by input I mean regular string to the field. 

 Thanks for the hint Petri, indeed we can support the event id from the homepage too.
Currently you can load it with njump.me/e/<event-id>

Proper error handling is on my roadmap! 

 Error page added and /<hex-id> fallback supported 

 That was fast!