You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
when a source bootik send a nostr notification for whitelisting, track it in database
When my Bootik receives a link notification on nostr, track it on database and display it on "Whitelist Requester" tab (every one) and "Pending links" (for the pending ones)
when accepting or refusing an association, send a nostr notification back to the source bootik
message is either "I refuse the link {ID}" or "I accept the link {ID}"
UI
On /admin/crossbootik 3rd tab "Association requests", display 3 tabs
1st tab : "Pending links"
Display every non-review link request from other Bootiks :
column 1 : Bootik's official name
column 2 : Bootik's npub
column 3 : Bootik's logo
column 4 : Bootik's URL
column 5 : association's type request
Referral
Association (Multibootik)
Discovery (Metabootik)
column 6 : Bootik's internal name input (allow you to nickname this Bootik if you accept the link)
column 7 : "Accept" button
column 8 : "Decline" button
2nd tab : "Whitelist requesters"
Display every bootik (from newer to older) that has sent a whitelist notification
column 1 : Bootik's official name
column 2 : Bootik's npub
column 3 : Bootik's logo
column 4 : Bootik's URL
The text was updated successfully, but these errors were encountered:
For the nostr notification, we could probably add a tag for cross-bootik messages. The tag would mean to not autoreply if message isn't understood in case of protocol evolutions.
Also add tags in case of error or non-error messages
Following #168
Use case
UI
On /admin/crossbootik 3rd tab "Association requests", display 3 tabs
1st tab : "Pending links"
Display every non-review link request from other Bootiks :
2nd tab : "Whitelist requesters"
Display every bootik (from newer to older) that has sent a whitelist notification
The text was updated successfully, but these errors were encountered: