From 5a7ad8ac724e303e505b9a9603666e281cf5c5e2 Mon Sep 17 00:00:00 2001 From: John Bowdre Date: Sun, 17 Sep 2023 18:51:48 -0500 Subject: [PATCH] update notice type --- content/posts/easy-push-notifications-with-ntfy/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/posts/easy-push-notifications-with-ntfy/index.md b/content/posts/easy-push-notifications-with-ntfy/index.md index 359af2f..d11b5a1 100644 --- a/content/posts/easy-push-notifications-with-ntfy/index.md +++ b/content/posts/easy-push-notifications-with-ntfy/index.md @@ -27,7 +27,7 @@ Wouldn't it be great if there was a simple way to send a notification to your ph I thought it sounded pretty compelling - and *then* I noticed that [ntfy's docs](https://docs.ntfy.sh/install/) made it sound really easy to self-host the server component, which would give me a bit more control and peace of mind. -{{% notice tip "Topics are public" %}} +{{% notice note "Topics are public" %}} Ntfy leverages uses a [pub-sub](https://en.wikipedia.org/wiki/Publish%E2%80%93subscribe_pattern) approach, and (by default) all topics are public. This means that anyone can write to or read from any topic, which makes it important to use a topic name that others aren't likely to guess. Self-hosting lets you [define ACLs](https://docs.ntfy.sh/config/#access-control) to protect sensitive topics.