Thanks for the confirm.
nostr:npub13v47pg9dxjq96an8jfev9znhm0k7ntwtlh9y335paj9kyjsjpznqzzl3l8 any idea why Boston is seeing that note in his timeline, if it has no hashtags, and he does not follow and has not followed the npub previously?
nostr:npub1zafcms4xya5ap9zr7xxr0jlrtrattwlesytn2s42030lzu0dwlzqpd26k5, the mechanism is quite simple, it just adds the hashtag text to the onboarding post view as soon as the user tries to type anything.
However, the hashtag is optional, the user can delete it if they want to
Discussion
Good question.
I would guess that the hashtag was appended to the text, the user deleted it, but it remained in the “tags” field of the Nostr JSON payload somehow.
Let me check the event JSON
nostr:npub1zafcms4xya5ap9zr7xxr0jlrtrattwlesytn2s42030lzu0dwlzqpd26k5, yes, that seems to be the case.
This is larger than just onboarding too. I believe this issue might be triggered on normal posts if users write hashtags and remove them, or if other clients add hashtags to the Nostr JSON payload without displaying them on the content
