mirror of
https://github.com/binwiederhier/ntfy.git
synced 2026-05-09 08:26:00 +02:00
[GH-ISSUE #8] Look at mqtt #7
Labels
No labels
ai-generated
android-app
android-app
android-app
🪲 bug
build
build
dependencies
docs
enhancement
enhancement
🔥 HOT
in-progress 🏃
ios
prio:low
prio:low
pull-request
question
🔒 security
server
server
unified-push
web-app
website
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ntfy#7
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 @binwiederhier on GitHub (Nov 20, 2021).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/8
@binwiederhier commented on GitHub (Nov 26, 2021):
I looked at mqtt and various Go libraries. It looks like a neat technology and specs. Long story short: I think I'm gonna pass and not implement it for ntfy.
Reasons: It seems quite large for ntfy and for its use case. Lots to configure, lots to confuse people.
I could see implementing a MQTT client on the server side that we'd also publish to, kinda like firebase is implemented, basically just forward message to another pubsub system. But I'll only implement that of somebody really needs it.
Libraries:
@jangrewe commented on GitHub (Dec 12, 2023):
This would be awesome as lots of home automation projects use MQTT as their messaging bus! A typical use case would be openHAB just publishing its notifications to an MQTT topic as usual, and ntfy subscribing to that (user configurable) topic to ... well, notify. ;-)
Maybe even allow subscribing to multiple separate topics, to categorize where the notifications are coming from. My Frigate server would be a second candidate for a topic.