I made a post today and someone commented with extremely vulgar language. Is there no way to delete or remove it from the thread? I reported the user and the post. Just kinda sucks you can’t straight up block other people from commenting on your posts…
That’s going to be a big problem as Nostr scales
Login to reply
Replies (27)
Muting so that you have no idea they replied or not isn’t sufficient?
Nobody knows what client you’re using.
Inability to block others at the protocol level is a feature, not a bug.
They are replies not comments so they are notes themselves. Why should you be allowed to censor someone else's notes
Because it’s a reply to my post.
I despise censorship and value free speech as much as anyone but if I make a post and someone starts commenting extremely vulgar language that is fundamentally associated with me and my reputation.
Maybe it’s technically not feasible but I do think the author of a post should be able to remove replies.
You only own your posts not your whole thread
Well that’s going to prevent a lot of users from coming to nostr
Its called free speech

A few people that i follow muted another reply to Kendy from the 'based truth' bot so it showed up as something I had to click in order to see. Should be sufficient for replies that reasonable people dont want to see.
On amethyst btw
you just need to set a trust level threshold on what notes you will see
How do you do that?
Definitely a problem, not everything is about censorship.
use Jumble or my Jumble fork
Funny thing is that I don’t have an issue with this. Actually tasteful not vulgar
Will look into this
One practical solution is to build personal relays into clients where you can block people from downloading your content and comments. If you block an nsec, the relay would refuse too send or receive any messages from them.
Hide reply is not available? I have seen it somewhere. I use #damus #primal #jumble & #wisp and I am too wiped from the farmers market to chase down the evidence right this minute.
(a) mute them
(b) use Web of trust
(c) only use permissioned relays (nuclear option, at that point you might as well just be on Mastodon)
I think the mistake is thinking you somehow "own" the space of replies to your post. That doesn't happen on a free network.
It might not always be awesome but it's still better than censorship & you need to be consistent
To understand why this is not possible, you have to understand what a regular note is, and what a reply is on Nostr.
When you create a regular note (kind 1), your client attempts to save that note to whichever relays you have listed as your "write" or "outbox" relays. Those relay operators may have rules that prevent your note from being written there. For instance, that relay may only accept notes from npubs that have paid to use it. If the relay owner doesn't prevent you from writing to that relay, then no one else can. They can opt not to see your notes, by adding your npub to their mute list, and for the default follow feed, they won't see your notes anyway unless they follow you.
When someone replies to your note, it isn't really tied to your note or the relays your note is stored on at all. Instead, the reply just has a tag that references your note's unique ID. For instance, the unique hex ID of your note that I am replying to is '6bb13ac00d3be47ad0f910af6427a9abd78fbe309e87ab5ec5fec2f14b4fc059,' and every reply in this thread will have a reference to it in the tags of their replies. There is absolutely no way for you to prevent anyone from adding that tag referencing your note into their reply. You have no authority over what they put in their note. Whatever client they use then requests to write their note to their write relays, and, if the client supports the outbox model, to your "inbox" or "read" relays. If the relay owners allow that npub to write to their relay, then there is nothing you can do to prevent the note from being written to those relays and showing up as a reply to your note.
Now, while there aren't ways to prevent others from replying to your notes, there are ways to not see their replies. The main way, and the most effective way, is to be selective about which relays you use as "read" or "inbox" relays. They should only allow reputable people to post to them. Web-of-Trust (WoT) relays are good for this, as are paid relays. I particularly like Spatia-Arcana's inbox relay, because it only allows notes that are written by someone within the WoT of the members of that community relay, and membership is invite only.
Speaking of relays... I was unable to find a relay list for you at all. What client are you using? I am going to guess Primal, based on your NIP-05 address and Lightning address. If so, then changing what relays you use will be futile, since Primal doesn't read from relays directly at all. Your only option is to mute the person and move on.
Other clients like Jumble and Coracle allow you to select what WoT score an npub must meet before you will see their notes. This can also be useful for not seeing unwanted spam and offensive content in your replies. Again, though, it doesn't mean the content isn't there; just that you can't see it.
Finally, there are a couple specialized relays called lockbox relays. When you write to them and no other relay, only npubs YOU HAVE FOLLOWED can read your notes. This drastically reduces your reach, as almost no one will see your notes, but then, neither will the spammers and jerks.
Bottom line: If you want to have more control over what you see in your replies, you are going to need to get away from Primal and use some quality inbox relays.
Thank you for sharing this. I need to learn more
Absolutely happy to help! Nostr is very simple to get into, but you really unlock how powerful it can be when you start learning about how it works and which clients allow you to make the most use of that architecture.
Anyone who approaches Nostr like it should have the same sorts of tools as centralized social media will result in disappointment and ultimately leaving, not realizing that the centralized nature of those platforms is the only reason those tools work at all. If Nostr is going to actually BE decentralized and censorship resistant, then there will need to be very different approaches to curating the content you see as a user. More of the responsibility will fall on you by necessity. There is no way around that without compromising decentralization and censorship resistance.
I did forget to mention one other method for hiding content you don't want to see. You can not only mute specific npubs, but you can mute words, too. Primal allows you to do so in the app and on the web by going to Settings>Muted Content>Words and adding any word that you think would not be used except in a context that you don't want to see it.
Respectfully, “fundamentally associated” is an overstatement in this context. Are you saying celebrities reputations are inextricably linked to every word of every reply to their social media posts until someone deletes or blocks them? PR doesn’t work like that…
Minimally reasonable people will not judge you based on vulgarity of replies of your posts. If they do, they’re probably dumb enough that their opinion doesn’t matter. On a permission-less protocol, you’re not responsible for what others say in your replies.
Although it’s your right to find or create a client that allows to filter and police how you see fit.
Yeah I totally get that. Fair point and appreciate this perspective. But if this is the case then we don’t “own” anything here. If I own a house and someone comes in and shits on the kitchen table I can kick that person out and never deal with them again… hope that analogy makes some sense. I guess this is hust how it is. We dont own our posts on Nostr
That analogy has merit.
I never considered the potential that ownership of Nostr events/posts requires unilateral authority over which npubs can reply or interact with the post or how their interactions are handled after submission at the protocol level.
After reconsideration, I believe that is already possible as a relay host. Without hosting a relay, I doubt you have unilateral ownership. Even with key-pair ownership.
@npub1n0st...k6h0 or @Wisp work quite well too