From 10c614faae60db62c81d1a34b20d6718d850f1be Mon Sep 17 00:00:00 2001 From: Arlind Ukshini Date: Mon, 27 Apr 2026 10:57:20 +0200 Subject: [PATCH] events: clarify 'forced' semantics in docs --- OPERATIONS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/OPERATIONS.md b/OPERATIONS.md index a1cd2b9..2884480 100644 --- a/OPERATIONS.md +++ b/OPERATIONS.md @@ -109,7 +109,7 @@ sudo -u fenja node /opt/fenja/bin/events.js stats Events recorded: - `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: