docs(wiki): say how long a key renews and what a new registration needs

2026-11-13 07:40:59 +00:00 · 2026-10-29 17:34:09 +01:00
parent 6d245ab4da
commit cd5ce4b1d9
1 changed files with 1 additions and 1 deletions
@@ -65,7 +65,7 @@ The OpenStreetMap layers are kept apart from the place rows and are joined only

 ## Installation key and daily allowance

-On its first search an installation registers itself with the service in the background: it solves a small proof of work (a few seconds on a Raspberry Pi) and receives a key, which TREK keeps encrypted in its database and renews on its own after 60 of its 90 days. Nobody clicks anything, and the first searches do not wait for it; until the key is there, requests go out the way they always did and are answered from a shared pool.
+On its first search an installation registers itself with the service in the background: it solves a small proof of work (a few seconds on a Raspberry Pi) and receives a key, which TREK keeps encrypted in its database and renews on its own after 60 of its 90 days. Nobody clicks anything, and the first searches do not wait for it; until the key is there, requests go out the way they always did and are answered from a shared pool. A key renews on its own for up to a year after it lapsed, whatever release the installation runs; registering anew needs a TREK release from the last six months.

 The key carries a random installation id and nothing else: no address, no host name, no user. It lets the service give each installation its own daily allowance instead of one pool per network, and it is sent only to the hosts in `TREK_SERVICES_HOSTS` (`places.liketrek.com`, `photon.liketrek.com` and `valhalla.liketrek.com` by default), never to a copy you run yourself or anywhere else.