Glossonotif logs into glosso.ink, polls /notifications, dedupes notification rows, and sends new items to subscribed browsers. Push clicks open the Glosso post/comment URL when one is present.

Features #

Polls Glosso notifications on a fixed interval.
Polls Ranko every 30 minutes and pushes when raters increase, ratings increase by 10+, or another trait becomes revealed.
Sends Web Push notifications with VAPID.
Stores browser subscriptions locally.
Uses a small web UI for login, subscription, test push, and manual polling.
Shows install instructions in regular browsers, then enables push controls inside the installed PWA.

Hosted Instance #

The live glosson.mosphere.at instance is private and locked to the Glosso user alice. Other users should self-host their own instance.

End-User Install #

Open your Glossonotif URL and log in with your Glosso username/password.

iOS #

Use Safari. Log in, tap Share, tap Add to Home Screen, open the new home-screen app, then tap Enable push.

After enabling push, open Glosso Push once from the setup prompt, then use its Open Glosso button and log in there too. This keeps the first notification tap from getting swallowed by Glosso login.

If a push opens the gateway instead of Glosso, delete the home-screen icon and add it again so iOS refreshes the PWA manifest and service worker.

Android #

Use Chrome. Log in, install/add the app when prompted, open it, then tap Enable push.

After enabling push, open Glosso Push once from the setup prompt, then use its Open Glosso button and log in there too.

Android push can be unreliable because Google fucking sucks: battery optimization, notification permissions, and Play Services can delay or drop pushes. If it stops working, reopen the app and tap Enable push again.

Setup #

npm install
cp .env.example .env

Edit .env:

GLOSSO_USER=alice
GLOSSO_PASS=...
ALLOWED_GLOSSO_USER=alice
RANKO_POLL_MINUTES=30
GATEWAY_TOKEN=...
WEB_PUSH_SUBJECT=mailto:you@example.com

Run it:

npm start

Open http://localhost:3099/, log in with the Glosso credentials, then click Enable push.

HTTPS #

Web Push requires a secure origin, except on localhost. For phone use, run Glossonotif behind HTTPS, for example with Caddy:

glosson.example.com {
  encode zstd gzip
  reverse_proxy 127.0.0.1:3099
}

Systemd #

Example service:

[Unit]
Description=Glosso push notification gateway
After=network-online.target
Wants=network-online.target

[Service]
Type=simple
User=agent
WorkingDirectory=/home/agent/glossonotif
EnvironmentFile=/home/agent/glossonotif/.env
ExecStart=/usr/bin/node src/server.js
Restart=on-failure
RestartSec=10s

[Install]
WantedBy=multi-user.target

Runtime Data #

Runtime files are written under data/:

vapid.json: generated VAPID key pair
state.json: seen notification IDs, browser subscriptions, latest launch target, latest Ranko counters

These are intentionally ignored by git.

Checks #

npm run check
node --check public/main.js
node --check public/sw.js

Clone this repository

Glossonotif #