Public event sending for nostr #3555

Closed
opened 2026-02-28 03:33:28 -05:00 by deekerman · 1 comment
Owner

Originally created by @kehiy on GitHub (Aug 20, 2024).

not found

🏷️ Feature Request Type

Change to existing notification-provider

🔖 Feature description

I think the Nostr notifications must support public sending as well. It will send a public event for service changes.

✔️ Solution

We can add a new feature for the Nostr provider to publish event's based on NIP-1 without encryption and receiver.

Alternatives

No response

📝 Additional Context

No response

Originally created by @kehiy on GitHub (Aug 20, 2024). ### 📑 I have found these related issues/pull requests not found ### 🏷️ Feature Request Type Change to existing notification-provider ### 🔖 Feature description I think the Nostr notifications must support public sending as well. It will send a public event for service changes. ### ✔️ Solution We can add a new feature for the Nostr provider to publish event's based on NIP-1 without encryption and receiver. ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_
Author
Owner

@CommanderStorm commented on GitHub (Aug 21, 2024):

This is kind of niche/uncommon notification provider.
If you/someone else would like to contribute such a provider, here is the Contribution guide:
https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md

=> A contribution for whatever you need from that provider would be appreciated

For notification providers the testing effort is mostly offloaded to the contributor side (otherwise this does not scale)
=> Please make sure to include the screenshots we request in the contribution guide

@CommanderStorm commented on GitHub (Aug 21, 2024): This is kind of niche/uncommon notification provider. If you/someone else would like to contribute such a provider, here is the Contribution guide: https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md => A contribution for whatever you need from that provider would be appreciated For notification providers the testing effort is mostly offloaded to the contributor side (otherwise this does not scale) => Please make sure to include the screenshots we request in the contribution guide
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#3555
No description provided.