@byscott-io/where-is-waldo 0.1.7 → 0.1.8
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +7 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -238,7 +238,8 @@ See `docs/PRESENCE_ROSTER_PLAN.md` for the full mode matrix and tradeoffs.
|
|
|
238
238
|
their live sessions (multiple browser tabs, mobile, etc.):
|
|
239
239
|
|
|
240
240
|
```
|
|
241
|
-
{ id: 7, status: "active", devices: { web: "idle", mobile: "active" }
|
|
241
|
+
{ id: 7, status: "active", devices: { web: "idle", mobile: "active" },
|
|
242
|
+
last_activity: "2026-07-27T15:23:04Z" }
|
|
242
243
|
```
|
|
243
244
|
|
|
244
245
|
- `status` — highest activity across devices (the "active anywhere?" answer):
|
|
@@ -248,6 +249,11 @@ their live sessions (multiple browser tabs, mobile, etc.):
|
|
|
248
249
|
- `offline` — no live sessions
|
|
249
250
|
- `devices[platform]` — that platform's own status (answers "active on
|
|
250
251
|
**mobile**?" vs. "active at all?").
|
|
252
|
+
- `last_activity` — ISO8601 timestamp of the most recent input across **all**
|
|
253
|
+
the subject's live sessions (`null` when offline). The roster only
|
|
254
|
+
broadcasts on `status` transitions, so subtract against your own clock to
|
|
255
|
+
derive seconds-idle and apply client-side thresholds without a server
|
|
256
|
+
`timeout` change: `(Date.now() - new Date(m.last_activity)) / 1000`.
|
|
251
257
|
|
|
252
258
|
#### Configure
|
|
253
259
|
|