#146

feat: add support for Nix via a flake

s12d ago

← Back to list

01Issue

BugOpenSwamp Club

AssigneesNone

Relationships

#967 $identify events are never consumed — anonymous web history never binds to the account

Opened by keeb · 7/4/2026

The web app emits $identify at sign-in (lib/auth.ts → identify(userId, getAnonymousId(req)) in lib/telemetry.ts) to link the anonymous browser device to the account. Nothing on the telemetry side consumes it: the stats consumer (services/telemetry/lib/consumers/stats.ts, updateIdentityMap) only binds a device when an event carries BOTH username and distinct_id — and $identify carries the user id as its distinct_id with the anon id buried in properties.$anon_id, so it is ingested and ignored.

The gap is structural, not incidental: the moment a user signs in, resolveDistinctId switches their web events' distinct_id from the anonymous IP+UA hash to their user id, so the anon hash never co-occurs with a username on any event. $identify was the only bridge, and only the emitting half was built.

Impact (measured in prod, 2026-07-04): anonymous web devices strand as ghost owners in the ClickHouse score_grants ledger. They can only earn presence grants (10/device-day), so the score impact is dust — 63,210 points across all stranded web ghosts combined — but the anon→identified funnel story is broken for web: pre-signup browsing history never folds into the profile, and analytics can't connect the visitor who converted to the account they became.

Steps to reproduce:

Browse swamp-club.com signed out (events carry distinct_id = IP+UA hash).
Sign in — a $identify event with properties.$anon_id is ingested.
Inspect the Mongo identity_map entry for the user: the anon hash is never added; its grants stay owned by a ghost.

Fix sketch: consume $identify in the stats consumer — extract properties.$anon_id, resolve distinct_id (user id) to the username, and feed the pair through the existing updateIdentityMap path. Healing is retroactive by construction: identity is resolved at read time over the grant ledger, so the ghost's history folds into the user the moment the mapping lands, no grants rewritten. Caveat: the anon id is an IP+UA hash and churns with IPs, so only the most recent hash binds — the fix narrows the gap, it cannot close it retroactively for old hashes.

Explicitly NOT blocking the scoring read-flip cutover (keeb, 2026-07-04) — waived for scoring purposes; this is a funnel/analytics correctness bug. Context: scoring/scoring.md § "Course correction — reverse the shadow", prerequisite 2.

02Bog Flow

Open

7/4/2026, 8:03:36 PM

No activity in this phase yet.

03Sludge Pulse

Scorecard: beta/rc-only extensions show "not scored" despite successful scoring (GET /score resolves only latestVersion)

`swamp extension search --channel beta|rc|stable` ignores the filter — all channels + the no-flag default return an identical result set

Beta-channel extensions are never scored — perpetual 'Scoring is taking longer than expected'

feat: allow models to call other models mid-execution via context.runModel()

swamp-club: enable OAuth provider for swamp serve collective-based admission

extension update/install reports new version while on-disk pulled files stay old

command/shell: step with timeout + a surviving child process reports exit -1 despite command exiting 0

swamp serve startup/shutdown is very slow on large repo and lacks diagnostics

Vault push log overstates what left the machine: Pushed N vault file(s) to datastore counts every dirty file, not just vault files

serve-auth: mode: oauth — device grant client + collective-based admission

serve-auth: enable OIDC Provider + Device Authorization plugins in swamp-club

Orphaned data (migrated-away/deleted model) can't be GC'd or deleted

Docs: document swamp data prune (orphaned-data reclamation)

UAT: CLI coverage for swamp data prune (orphaned-data reclamation)

Session credential revocation scans entire credential map on every dispatch completion

Docs: update worker-commands.md for --all flag and JSON output change

datastore migrate-index aborts on hardcoded 30s S3 requestTimeout for large shards

swamp worker list: hide disconnected workers by default, add --all flag

swamp serve should survive bad extension failures

Worker fleets phase 7: how-to guides and explanation docs

swamp serve: catch unhandled promise rejections from extensions

[@adam/cfgmgmt] SSH helper can crash swamp serve via unhandled finally() rejection

Docs: add --server-token flag to worker connect reference

Add --server-token to worker connect for authenticated orchestrators

Docs: document --trusted-hosts flag for swamp serve

Document SWAMP_SERVE_EXTRA_HEADERS for reverse proxy/tunnel setups

Add --trusted-hosts flag to swamp serve for Docker/Kubernetes worker connections

Allow swamp clients to send custom headers when connecting to swamp serve

Docs: update serve-flags.md default queue timeout from 60s to 10m

Worker fleets phase 6: raise default queue timeout to 10 minutes

Worker fleets phase 4b: capacity slots and concurrent dispatch

MethodContext docs/comments mention context.putSecret but runtime exposes vaultService.put

Docs: add --concurrency flag and SLOTS column to worker-commands reference

install.sh still points users to systeminit/swamp

Support user systemd units for 'swamp serve daemon enable'

swamp serve scheduled execution runs steps in an isolated data scope: readResource sees empty state, writeResource never reaches the model-scope chain — stateful scheduled workflows duplicate instead of deduplicating

Support installing swamp via mise GitHub backend

Worker fleets phase 4a: dispatch runner extraction — child process per dispatch

Docs: add swamp worker daemon enable/disable/status to worker-commands reference

Worker fleets phase 3 PR2: swamp worker daemon enable

Docs: add drain, lifecycle policies, and exit-code contract to references

Worker fleets phase 3 PR1: drain state machine, lifecycle policies, signal handling

Leaderboard search excludes ghosts — a visible ghost can't be found by its alias

issue-lifecycle: plan lifecycle entry silently dropped when summary exceeds 1000 chars

Docs: add worker verify, --verify-on-enroll, and env-var config to references

Labs - Filters do not apply to Blocked status and Billing Tier category

Worker fleets phase 2 PR2: env-var config, swamp worker verify, --verify-on-enroll

Docs: add --type flag to issue edit reference and how-to

Docs: update manual with whole-field expression syntax for workflow task inputs/globalArgs

Allow changing an existing issue to security/confidential after submission

Allow dynamic object expressions for workflow task inputs/globalArgs

Docs: update enrollment token references for fleet tokens (--max-enrollments)

Worker fleets phase 2 PR1: fleet tokens (--max-enrollments, bindings, worker naming)

$identify events are never consumed — anonymous web history never binds to the account

Worker fleets phase 1 PR3: boot reconciliation and integration test

Login success still shows login tip

Support confidential visibility for non-security issues

Fine-grained scopes for swamp.club access tokens

Add associative info to user profiles: collective membership + collaborative contributions

Remove comments from /feed and redesign the page

feed_post_score_events queue grows unboundedly (no TTL, no delete-on-delivery)

Make paid subscribers visually stand out (badge, profile popup summary)

Relax the profanity filter

Giphy integration via /giphy command

@-mention autocomplete for users when writing lab ripples

Worker fleets phase 1 PR2: step_queued events, pending-dispatch model, queue introspection

Docs: add swamp worker queue to worker-commands reference

/lab shipped list is sorted by issue number, not ship date

Docs: update manual for ephemeral data and step-output dependency deferral

Docs: update remote execution references for elastic queueing

Support dynamic host discovery from external sources

Worker fleets phase 1: elastic queueing

catalog backfill should support scoped population for targeted lookups

Docs: document global skill sync behavior for custom tools in manual

swamp update syncs global skills to default agent directories instead of configured custom Pi skillsDir

coerceToSuffix does not sanitize path-unsafe characters, causing forEach items and vary dimensions with / to produce invalid data instance names

Badge for activity on other people's issues

swamp serve: add @keychain=<service>/<account> indirection for secret args on macOS

swamp serve: eliminate wrapper scripts via @vault= secret refs and native startup hooks

Automate mechanical frontmatter fixes in the fixing stage