Oh, the trailing exclamation point worked, too. I wonder if that's because it's punctuation.
note18j2zgc673mlnf3euynue4fk7k0lc2vky0ukfrenyge5gu2vqksessk676xTrying to break Iris.
Ah, predictable. Iris doesn't like it when chars are touching an npub or note ID.
If I'm right (when posted from/viewed in Iris)...
Okay: note18j2zgc673mlnf3euynue4fk7k0lc2vky0ukfrenyge5gu2vqksessk676x
Not Okay:note18j2zgc673mlnf3euynue4fk7k0lc2vky0ukfrenyge5gu2vqksessk676x
Not Okay: note18j2zgc673mlnf3euynue4fk7k0lc2vky0ukfrenyge5gu2vqksessk676x!
What happens if we try to prefix with "&" when referencing a note ID in Iris?
We get this: ¬e18j2zgc673mlnf3euynue4fk7k0lc2vky0ukfrenyge5gu2vqksessk676x
Worth a try!
#[4] does it make sense for my reply (sent from Iris) above to include a "p" ref tag to myself? I haven't checked yet if other clients are doing that, but seems unnecessary when I'm the person responding.
Yes. Your note ID ref in the content was converted to a pointer to the "d25e38" "e" tag.
The first "e" tag would be the note you were responding to (mine) and the "p" ref is who you were responding to (me). Other clients would have added "root" or "reply" to the first "e" tag.
Things are def not very standardized right now!!!
From which client?
Yep. So note ID refs in Iris just don't create an "e" ref tag no matter if I include the "@" or not.
And it looks like that lack of an "e" ref tag screws up some of the other clients.
Okay, so if I "@" reference a note ID from Iris, what will we get?
Here goes: @note16f0rs3ankx5762728u90kuhchp3250mkpvj829y4upfckx68fw0qtjyama
Nor in Snort.
Iris isn't adding any "e" ref tags in the raw json; it's just parsing the "note1..." text in the `content`.
Ooh, that worked beautifully!
A test post from Iris. Do I just drop a note ID as is?
Like this: note16f0rs3ankx5762728u90kuhchp3250mkpvj829y4upfckx68fw0qtjyama
#[1] I can see the above post in my feed but if I click on it, it kind of jumps and then renders blank.
But if I click on the response to that note (note1fxx5lw), they both render threaded fine.
Snort created the "e" tag w/"mention" but then renders blank when I click the note.
Iris just treats it like a response to the referenced event and hides the note ID from the content.
Amethyst also treats it like a reply but leaves the note ID clickable.
None of these outcomes were what I was expecting when "mention"ing an event.
A thread where I probably screw up a bunch of stuff in different Nostr clients.
Reference a note ID from Snort. No "@" sign?
#[0]
#[3] check the replies to the above post:
* Iris includes "root" and "reply" info in the "e" tags.
* Same for Snort.
* Amethyst only has unadorned "e" tags. The response is rendered correctly in Amethyst but it's somewhat orphaned and not properly threaded in Snort and Iris.
see: @#[4]
Test from Snort.
Test from Amethyst.
Test from Iris.