git404hub

what is autopush-proxy-poc fr?

eternal-flame-ad/autopush-proxy-poc — explained in plain English

Analysis updated 2026-07-18 · repo last pushed 2025-02-26

RustAudience · developerComplexity · 3/5StaleSetup · moderate

tl;dr

A proof-of-concept server built in Rust that lets you run your own web push notification relay, similar to Mozilla's service for Firefox, giving you full control over how notifications are delivered to users.

vibe map

mindmap
  root((repo))
    What it does
      Custom push relay server
      Replaces Mozilla service
      Routes notifications to browsers
    How it works
      Websocket browser connections
      VAPID header verification
      ECDH key exchange
    Use cases
      Privacy-focused products
      Regulated data environments
      Learning push pipelines
    Tech stack
      Rust
      Websockets
      Cryptography
    Status
      Proof of concept
      Encryption incomplete
      No production deployment
    Audience
      Self-hosting developers
      Privacy-conscious builders

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

what do people make with this?

VIBE 1

Run your own web push notification relay server for Firefox instead of relying on Mozilla's service.

VIBE 2

Learn how the web push pipeline works by inspecting and modifying a working relay server.

VIBE 3

Build a privacy-focused product where push notification data stays entirely on your own infrastructure.

what's the stack?

RustWebSocketsVAPIDECDH

how it stacks up fr

eternal-flame-ad/autopush-proxy-poc0xr10t/pulsefi404-agent/codes-miner
Stars00
LanguageRustRustRust
Last pushed2025-02-26
MaintenanceStale
Setup difficultymoderatehardmoderate
Complexity3/54/53/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

how do i run it?

Difficulty · moderate time til it works · 30min

Requires running a Rust server with a secure websocket (wss://) connection and changing a Firefox browser preference to point at your server's URL.

in plain english

Web push notifications work through relay servers that sit between websites and browsers. Mozilla operates such a service for Firefox, and the "Autopush Interceptor" is a proof-of-concept project that lets you run your own version of that relay server instead of relying on Mozilla's. This matters if you want full control over how push notifications are delivered to your users, for example, if you're building a privacy-focused product, operating in a regulated environment where data must stay on your own infrastructure, or just want to understand how the push pipeline works. The server handles two sides of the push equation. On the websocket side, it accepts connections from browsers, responding to "hello" and "register" requests so that a browser can subscribe to push notifications through your server instead of the default. On the ingestion side, it decodes and verifies the cryptographic headers (VAPID) that websites send to authenticate their push messages, and it handles the key exchange (ECDH) needed to route messages to the right browser. A couple of pieces are still unfinished: unregistering subscriptions and relaying official broadcasts aren't implemented yet, and end-to-end encryption verification is marked as a work in progress. To use it, you run the server and point Firefox at it by changing a browser preference to your server's URL. You need to use a secure websocket connection (wss://) unless you explicitly enable insecure connections for testing. This is built in Rust and is explicitly a proof of concept, so it's more of a learning tool or starting point than something you'd put in production today. The README doesn't go into detail about performance, scaling, or deployment considerations, which reinforces that this is early-stage experimentation. Anyone considering it should understand the security implications of running a custom push relay, especially since parts of the encryption and verification flow are still incomplete.

prompts (copy fr)

prompt 1
Help me set up this Rust autopush proxy server locally and configure Firefox to use my custom push relay URL instead of Mozilla's default
prompt 2
Explain how VAPID authentication and ECDH key exchange work in this autopush interceptor so I can understand how push messages are verified and routed
prompt 3
Help me add the missing unregister subscription feature to this Rust push relay proof-of-concept
prompt 4
Walk me through the security implications of running my own web push relay server, especially since end-to-end encryption verification is still incomplete in this project

Frequently asked questions

what is autopush-proxy-poc fr?

A proof-of-concept server built in Rust that lets you run your own web push notification relay, similar to Mozilla's service for Firefox, giving you full control over how notifications are delivered to users.

What language is autopush-proxy-poc written in?

Mainly Rust. The stack also includes Rust, WebSockets, VAPID.

Is autopush-proxy-poc actively maintained?

Stale — no commits in 1-2 years (last push 2025-02-26).

How hard is autopush-proxy-poc to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is autopush-proxy-poc for?

Mainly developer.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.