#146

feat: add support for Nix via a flake

s12d ago

← Back to list

01Issue

FeatureShippedSwamp Club

AssigneesNone

Relationships

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

Opened by webframp · 7/3/2026· Shipped 7/4/2026

PR #819: https://github.com/swamp-club/swamp-club/pull/819

Problem

The user profile (e.g. /u/webframp) is a strong record of what a person did alone: the CLI-usage sunburst, published extensions, writings, tier, streak, and badges. What it does not show is the associative layer — who a person is connected to and what they built with others.

Today a visitor cannot tell:

which collectives a user belongs to, and
what collaborative artifacts they produced — merged issues, shipped fixes, and similar contributions that landed in someone else's or a collective's work.

The profile should do double duty: prove contribution (credibility) and convey level of engagement and standing.

Proposed solution

Add an associative section to the profile that surfaces:

Collectives the user belongs to (collectives are explicit orgs/teams you join). Public collectives always show; private collectives appear only when the user opts in to reveal them on their profile.
Collaborative contributions — merged issues and shipped fixes — presented as a scannable, linkable record.

Preferred presentation (open to iteration): a collective-anchored view where each collective the user belongs to expands to show the contributions shipped under it, with one compact relational visualization the visitor can click into to explore connections. This matches the existing click-into-detail feel of the points sunburst without resorting to a hard-to-read network graph.

Points are out of scope. Points continue to display as they do today and stay earned separately by actual events and activity; this feature does not tie the associative data to scoring.

Alternatives considered

Flat sections — two new card lists (Collectives, Shipped Contributions) mirroring the existing Extensions and Writings sections. Simplest and most consistent, but the least associative.
Relational constellation — a full network graph centering the user, with clickable collective/collaborator/artifact nodes. Most visual, but graphs are hard to keep readable and risk feeling flashy over useful.

#933 — "Add a 'my collective extensions' filter to extensions page" (adjacent collective-surfacing work, different surface).

02Bog Flow

Shipped

7/4/2026, 6:01:04 AM

No activity in this phase yet.

Linked PR #819https://github.com/swamp-club/swamp-club/pull/819

03Sludge Pulse

jeremy commented 7/3/2026, 7:50:53 PM(edited)

I would like to add a gif of support to this issue. Imagine a noble capybara nodding in approval.

keeb commented 7/4/2026, 3:02:50 AM

@jeremy - great idea, we have debated integrating giphy here. We probably should, eh?

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