Ideas recorded for later. Nothing here is designed or approved; each needs its own design pass with the user before any work starts.
Telling a player who is not connected that something needs them: an invitation, their turn, a move by the opponent, a game ending, a turn clock running low.
To think through before building:
- Which events deserve a notification at all, and how players choose (per event, per game, quiet hours, a digest).
- Channels: email (we already send sign-up mail through an SMTP relay, with strict caps and bounce rules), ActivityPub/Mastodon direct posts (readable by server admins, so never hidden information), and anything a period client can show when it next connects (an inbox at sign-in).
- Abuse and cost: invitations from strangers, floods, sending limits and reputation (docs/accounts.md, email sending limits), opting out, and never revealing private information.
- Privacy: what a notification may contain (no hidden game state), where addresses are stored, and deletion.
- Layering: notifications stay a separate layer that observes table events (docs/architecture.md), never part of the core or the games.
- GEnie RSCARDS front ends through a modem or serial bridge (research: docs/research/bg-client-genie-rscards.md). Lower priority.
- GGS server extension for Reversi (port 6504).
- The 2027 side of the web port: JSON API, canvas and WebGL clients.
This doc on GitHub
| | These pages cover every ParlorNet server. | Source code | ParlorNet is free software. |