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