Great idea! I’ve already added pow support to it 👍

Vibe coded a Nostr comment component :FLASHBANG:
https://nostr-comments.pages.dev/

Old issue, the browser blocked new websocket connections, which caused the timeout.

This is key info.

Sure 👍

Jumble’s relay info is rendered just like a regular post, it supports images, embedded posts, and so on.

It’s mainly just my personal feeling that it’s not really necessary.

That’s still content they chose to publish, so of course it won’t be hidden from the timeline. What it does is prevent your notifications tab from being polluted, so you don’t miss important notifications because of all the noise.

I get what you’re asking for, and I understand the desire for that level of control. That said, the benefit of this feature doesn’t really feel worth the cost to me.

If it’s just a single note, it won’t stay in your timeline for long anyway—it’ll quickly get pushed out by newer content. But once you add a “hide this specific note” feature, every note would need to be checked against a list of notes you’ve chosen to hide before being shown. Sure, there are ways to optimize this, but the question is: is it really worth it?

That hidden-notes list would also keep growing over time. You might be disciplined and keep it small, but other users probably won’t, and that complexity adds up fast.

The purpose of “hide indirect” is to deal with hell threads, that is, to hide replies from other users to the note shown in your screenshot.

As for the case you mentioned:
* If the account is just spam, you can easily filter it out using the trust filter.
* If it’s a normal account but you personally find them annoying and don’t want to see their content, you can simply mute them.

The reason you’ve only run into it twice so far is simply because bad actors haven’t shown up yet. Once they do, blocking won’t really help.

Blocking the original user doesn’t solve the hell thread problem, because the issue isn’t the original note itself, it’s the flood of replies from many other people.

I think hiding indirect notifications is sufficient here

Honestly, manual blocking isn’t a real solution, this spam is super easy to mass-produce, so users can’t block every single one. Their blocklists will just keep growing unwieldy and ruin the client experience.