mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Public event sending for nostr #3555
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#3555
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
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
@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