Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

blossom: bud-09 reporting blobs. #38

Open
kehiy opened this issue Jan 29, 2025 · 2 comments
Open

blossom: bud-09 reporting blobs. #38

kehiy opened this issue Jan 29, 2025 · 2 comments
Assignees

Comments

@kehiy
Copy link
Contributor

kehiy commented Jan 29, 2025

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:

  1. sending them to operator pubkey as dm. (notification)
  2. 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.

@mikedilger
Copy link
Owner

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.

@kehiy
Copy link
Contributor Author

kehiy commented Jan 30, 2025

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants