FrogTalk Development & support
AU-hosted testbed for the dev branch. Imageboard title FrogTalk Development & support · topic dev. Federation and mobile QA happen here before promotion to the main hub.
The development instance on frogtalk.xyz ships the dev branch first — API changes, mobile builds, and federation fixes land here before frogtalk.app. Open PRs, run your own Lilypad (node), and test cross-Lilypad chat without touching production users. Pre-alpha: not audited; do not store sensitive data here.
AU-hosted testbed for the dev branch. Imageboard title FrogTalk Development & support · topic dev. Federation and mobile QA happen here before promotion to the main hub.
Dev (.xyz) | Main (.app) |
|---|---|
| Latest merged PRs | Promoted pre-alpha hub |
| May reset or 502 | Best-effort uptime |
| Test federation here | Official directory |
| Client default: .xyz | Client default: .app |
Fork → branch from dev → test on this node or locally → PR into dev → after review, changes merge to master for frogtalk.app. Hub directory and release hashes always reference frogtalk.app.
Signal Protocol DMs and AES-GCM private channels — verify ratchet, safety numbers, and key rotation after server changes.
Join against frogtalk.app, pin peer keys, push inbox/outbox traffic, and confirm board peer pills sync.
Point the app wizard at frogtalk.xyz (default on dev branch). Test APK handoff and WebSocket stability.
Exercise live bridge sync, media, and voice notes on a non-production node before promoting config.
Board identity: Development & support · topic dev. Test moderation and federation nav.
Hit /docs/api and Server Admin flows — federation tokens, contacts, release hash checks.
dev first.devClone github.com/deadinternetfox/frogtalk, create a feature branch off dev, not master.
bash node/scripts/install.sh setup — or test against frogtalk.xyz/app after deploy.
devOne focused change per PR. Note federation / mobile impact in the description.
masterAfter review and QA here, merge to master for frogtalk.app. Only client/official-node.json differs between branches (.xyz vs .app).
The official directory and hub registration always use frogtalk.app. This node should appear as a peer after node_federation_join.sh — verify hash badges, onion handoffs, and release feed polling against the main hub.
:8080) so you can exercise federation, bridges, and the dev branch without touching production users. Front it with nginx / Cloudflare for TLS.git clone -b dev https://github.com/deadinternetfox/frogtalk
cd frogtalk && docker compose up -dDev runs the same client-side encryption as main, but databases may be wiped, configs may break, and code is unaudited.