Global Feed Post Login
Replying to Avatar daniele

It seems that every client except Gossip still wrongly manage the notifications, flooding the user when a large thread starts:

Ex. in #[7] I was just mentioned (I didn't replied) and I'm receiving notifications for every reply because they include *all* the mentioned users in the first note as p-tag [*]

Proposal: why don't show only the notifications that are a direct reply to the user's note or are in his gerarchy (reply of reply)?

Or at least separate and giving them a different highlight related to their importance.

To notify direct replies (or the gerarchy) a client can use as reference the e-tag's npub instead of the p-tags.

[*] I suspect that the notification problem starts from the event structure, NIP-10 stated:

> When replying to a text event E the reply event's "p" tags should contain all of E's "p" tags as well as the "pubkey" of the event being replied to.

So p tags are accumulating at every reply, why is this necessary?

/cc #[1] #[0] #[5] #[2] #[3] #[6] #[4]

(This way we can test the issue realtime 🤣)

Avatar
KoalaSat 2y ago

Never thought about this but it should be easy to identify whether the list of tagged events belongs to the user or not by looking into the DB, I'll think about this thanks for heads-up!

Reply to this note

Please Login to reply.

Discussion

Avatar
daniele 2y ago

You are welcome, and thanks for you work on Nostros, it is really nice :)

Thread collapsed