~ knotless Search/
↑↓ move↵ open⇧↵ all results

hum.delve.town/at_mcp

hum's fork of GroveResearch/at_mcp. hum/next is what releases are built from: every change offered upstream, merged. listeners is the listener work in progress (docs/listeners.md). Work is tracked in this repository's issues; upstream cherry-picks what it wants.

at_mcp 0.3.3-hum.4 Pre-release 1 package

0
0

Notifications as a source for listeners

Open
Open hum.delve.town opened this issue 0 comments

Thickening the steel thread (see the tracking issue). The thread runs on Spacedust links alone. Social-app mentions, replies and quotes are links too, so the built-in listener already hears them.

Notifications add what links can't give:

  • the AppView's own moderation and labels;
  • seenAt, which the app's unread count is kept from;
  • a read that reaches back further than Constellation's index.

Design: docs/listeners.md, the Sources table.

Do: a notifications source for listeners, with reasons as its filter, fed by the existing collector (AtMcp.Notifications, one listNotifications a minute per account). The built-in listener takes reply, mention and quote from it too. The same record reached by a link and by a notification is one update. Acknowledging the built-in listener also moves the network's seenAt, to the newest acknowledged update's indexed_at, never to now.

Tests that would show it wrong

  1. A reply that arrives by Spacedust and by notifications is one update.
  2. Acknowledging the built-in listener through update N moves seenAt to N's indexed_at, and a notification indexed after it stays unread in the app.
  3. A notification reason not asked for (like, follow) is not an update.