Choosing an app id
The app id is the last part of the lane URL. It decides where your data lives — it is a routing key, not a password.
Format
- 1–64 characters of
a-z,0-9,.,_and-. - Must start with a letter or a digit.
- Upper-case letters are folded to lower case:
/app/MyGameis the same lane as/app/mygame. The/app/prefix itself must be lower case. - A trailing slash is fine. Anything else — spaces, extra path segments, an empty id — is refused with an
invalid app lanenotice.
Known tenants and public lanes
Every valid id is served. What changes is where the data is kept:
| Known tenant | Public lane | |
|---|---|---|
| Who | Ids on the relay's tenant list | Every other id |
| Storage | Its own storage | Shared with other apps (8 shared shards, chosen by a hash of the id) |
| Retention | Regular events up to 7 days, addressable 30 days | 2 hours for both |
| Addresses per author and kind | 64 | 16 |
To be added to the list, open a GitHub issue describing the app. Joining or leaving the list moves the lane to different storage: data kept before the move stays behind until it expires.
It is not a secret
Anyone can connect to any lane id, including yours. Lanes separate traffic and storage; they do not authenticate apps. Do not rely on an obscure id for privacy.