<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Ntfy - 标签 - 研发日志 · R&amp;D Log</title><link>https://rd163.visword.com/tags/ntfy/</link><description>Ntfy - 标签 - 研发日志 · R&amp;D Log</description><generator>Hugo -- gohugo.io</generator><language>zh-CN</language><managingEditor>whutluohui@gmail.com (小智晖)</managingEditor><webMaster>whutluohui@gmail.com (小智晖)</webMaster><copyright>本作品采用知识共享署名-非商业性使用 4.0 国际许可协议进行许可。</copyright><lastBuildDate>Sat, 31 May 2025 00:00:00 +0800</lastBuildDate><atom:link href="https://rd163.visword.com/tags/ntfy/" rel="self" type="application/rss+xml"/><item><title>通知推送服务方案</title><link>https://rd163.visword.com/posts/notify-push-service/</link><pubDate>Sat, 31 May 2025 00:00:00 +0800</pubDate><author><name>小智晖</name></author><guid>https://rd163.visword.com/posts/notify-push-service/</guid><description>&lt;p>在服务端开发与运维场景中,常常需要把监控告警、构建结果、定时任务状态等信息以推送通知的形式实时发送到手机或桌面。直接接入各厂商的推送通道(APNs、FCM)成本较高,而第三方 SaaS 又涉及数据出境和付费问题。此时,&lt;strong>自建通知推送服务&lt;/strong>成为一种兼顾可控性与简洁性的选择。&lt;/p></description></item></channel></rss>