Remove irrelevant notices for new users #681
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Kieran/snort#681
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
Currently new users see a donation notice and a zap split notice. I think either is necessary, and Tanel thinks this as well and pointed it out in his Snort review video.
@Karnage We can hide these tasks for the new user and in order to determine if a user is a new user we can maintain a state in sessionstorage when they signup but when do we show these tasks for this user? I mean to ask when do we consider this user is no longer a new user?
One thing that can be done is when the user logs out of snort and logs back in we can set this newuser state to false and start showing the tasks. But most likely the users wont logoff from the applications if it is being used from desktop. So what do we do?