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
you can assign it to me. but there is an open question:
how we are going to use this report list?
for this project 2 things is possible:
sending them to operator pubkey as dm. (notification)
making them available from nip-86 API.
im my own relay and media server i would follow second approach to trait with reports. (but their are not compatible with nip-86) and i would support it on mangostr (nip-86 native).
note: if you assign it to me it may takes a little time since im not a good rust coder.
The text was updated successfully, but these errors were encountered:
Initially I'm in support of (2). Later on after relays can generate events (chorus doesn't) they can send a short DM to the operators letting them know that they should check the NIP-86 management panel.
NIP-86 was just what fiatjaf and I were doing, it is not complete. You just added a new command in that last PR. Just add more methods as you need them.
good. i agree with that. i would keep #39 as a higher priority. since supporting blossom reports and managing blossom itself may need a new bud for the blossom server manager. we can think better on this. about #39 we need it more at the moment.
you can assign it to me. but there is an open question:
how we are going to use this report list?
for this project 2 things is possible:
im my own relay and media server i would follow second approach to trait with reports. (but their are not compatible with nip-86) and i would support it on mangostr (nip-86 native).
The text was updated successfully, but these errors were encountered: