<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Push-Service on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/push-service/</link>
    <description>Recent content in Push-Service on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 01 May 2026 15:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/push-service/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Web Push Notification Servers — Complete Deployment Guide</title>
      <link>https://www.pistack.xyz/posts/2026-05-01-self-hosted-web-push-notification-server-comparison/</link>
      <pubDate>Fri, 01 May 2026 15:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-01-self-hosted-web-push-notification-server-comparison/</guid>
      <description>&lt;p&gt;Delivering real-time notifications to users&amp;rsquo; browsers without relying on third-party services like OneSignal or Firebase Cloud Messaging is increasingly important for privacy-focused applications. The Web Push Protocol, standardized by the IETF, allows any server to send push notifications to browsers that support the Notification API. In this guide, we explore how to self-host web push notification infrastructure using open-source tools, and compare the key components you need to build your own notification stack.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
