Notification Spam #376
Labels
No Label
1000k
100k
10k
200k
20k
500k
50k
5k
75k
backend
blocked:design
bug
dependencies
documentation
duplicate
enhancement
good first issue
help wanted
invalid
P1
P2
P3
question
scope:intl
scope:nip
scope:query_tracing
scope:ux
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Kieran/snort#376
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The zappr (npub1hswpe3sy2wdmgzzyd9nl8r32gc7nhkh60tmlx9er5dfk9u0f40qst048qg) bot tagged about 200+ pubkeys in a note, in which hundreds of people decided to reply to that note (note1ve7z2zsg67ragphw4d40ywgj0zwyyzjpuyd85cp35xdeg4p9nzjsreqzha).
This yielded hundreds of notifications, in which everyone was replying about how it was destroying their notifications.
Replies and other events associated with a note that a pubkey was tagged I don't think should yield a notification to that pubkey.
Also, could be nice to be able to delete notifications.
Is there planned any work on "anti-hell-threads" in Snort @v0l? Notifications gets obliterated from hell-threads with 1300+ tagged users.
Still?