Subnostr

I think that for a Nostr client would be optional to split personal notification (reply/reaction to a personal post) and the generic thread activity.

This and the indipendent "only post" and "post + reply" feeds help a lot to improve the signal vs noise factor.

These points also promote a more aware use of the social network: more focus, less wasted time.

Do you know any client that already apply this paradigm, both parts?

yunginter.net 3y ago

this is only an issue because most clients don’t have a way to customize “replying to” although many have been motivated to implement this feature due to this recent mega list (sans a disclaimer to respect the mentions of the devs and not reply to the list). Disclaimer won’t be necessary when I can uncheck the people I don’t want to tag. This works two ways… so if you were replying to 5 people including me and I felt like the conversation had drifted away from the need to tag the 4 other people, I would respond only to you, and your only choose is to start a new thread manually tagging these people or to only reply to me.

You shouldn’t be receiving reactions to posts that you are simply tagged in.

Reply to this note

Please Login to reply.

Discussion

daniele 3y ago

NIP-10 (https://github.com/nostr-protocol/nips/blob/master/10.md) tell us how to manage replies. If a post is a reply the client can clearly identify the event and so the author; in my view only this one should receive a notification in the "strict feed".

The open feed could include all notification related to the root or, if the client is smart, only from the post I replied to, so the sub branch.

A tagging mechanism require users attention, and users are lazy (I daily struggle with users that cannot use email carbon copy properly...), I dubt it will work. Perhaps a personal mute thread/branch function can be useful, but would be a pure client implementation.

#[3] #[4] #[5] #[6] #[7] #[8] #[9] #[10]

ideas?

daniele 3y ago

> You shouldn’t be receiving reactions to posts that you are simply tagged in.

Agree.

But depends on what you mean with "tagged". Explicit tag with @ should always be honoured, with the exception of blocked users.

If you refer to the "p" tag of the specs I double agree, I suspect clients use this to fire the notifications, while I suggest to focus the events and get the relations with the authors.

This fixes the "bad behaviour" of stuffing pub keys of every post in a thread.

NIP-10 doesn't seem to address the reply of reply case: https://github.com/nostr-protocol/nips/blob/master/10.md#the-p-tag

yunginter.net 3y ago

relax a bit, let the clients get out of beta.

Technically, clients only need to follow nip 01.

by tagged I mean mentioned in by a user putting your pubkey… of course the original author a1 should receive the reactions to their note.

If a client is sending me notifications that your reply to me was liked, I won’t use that client.

that’s the beauty of that technicality, and what makes nostr so great.

fiatjaf 3y ago

My old client only included the last 4 "p" tags from the previous notes, I think, it didn't copy all to prevent this kind of flooding.

daniele 3y ago

What are you using?