joh/customer-presentation
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

events: clarify 'forced' semantics in docs

Browse source
This commit is contained in:
Arlind Ukshini 2026-04-27 10:57:20 +02:00
parent 32c88041ec
commit 10c614faae
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
OPERATIONS.md
View file

@ -109,7 +109,7 @@ sudo -u fenja node /opt/fenja/bin/events.js stats
Events recorded: Events recorded:
- `login` — written on `POST /auth/login` success. One row per fresh login (cookie-loss re-logins included). The `meta` column is empty. - `login` — written on `POST /auth/login` success. One row per fresh login (cookie-loss re-logins included). The `meta` column is empty.
- `timeline_view` — written on every `GET /timeline`. `meta` is `{view: "mobile"|"desktop", forced: true|false}`; `forced=true` means the user passed `?view=mobile` or `?view=desktop` to override the UA guess. - `timeline_view` — written on every `GET /timeline`. `meta` is `{view: "mobile"|"desktop", forced: true|false}`; `forced=true` means the user explicitly passed `?view=mobile` or `?view=desktop` (regardless of whether that matched or overrode the UA-derived choice).
For ad-hoc SQL: For ad-hoc SQL: