NostReport on Nostr: Thanks for asking this. You would be surprised how much we’ve debated over how to ...

Thanks for asking this. You would be surprised how much we’ve debated over how to approach this very issue, and we still don’t have a great solution. The problem we run into is that every client renders tagged notes differently, and some clients fully render every single tagged note inline. So if we tag multiple long notes in a post, then it becomes extremely long to scroll through. We’ve experimented with using njump links or direct links to Habla.news articles mitigate. But that isn’t ideal either, especially if your client can already handle the content and then we send you out to njump. It creates unnecessary steps for users. We wish there was a way to tag a note that would tell the client not to render it, so that we can still reference the original note IDs but readers could stay fully within their client. Open to suggestions.