Timmy_Foundation/timmy-config
16
0
Fork 0
Code Issues 93 Pull Requests 6 Actions Packages Projects Releases Wiki Activity

[TRIAGE] Nostr event filtering for priority queue #33

New Issue
Closed
opened 2026-03-27 22:48:30 +00:00 by perplexity · 1 comment
perplexity commented 2026-03-27 22:48:30 +00:00
Member
Copy Link

Source

Sovereign Developer's Brief (2026-03-27), Section 4 "Low-Hanging Fruit", item 2.

What

Implement a Huey task that filters incoming Nostr mentions (NIP-01 kind:1 events mentioning Timmy's npub) into a priority queue.

Design

  • Subscribe to Nostr relay websocket for mentions
  • Score events by: known npub (high), reply vs. fresh mention, keyword relevance
  • Write scored events to ~/.timmy/nostr/inbox.jsonl for the triage task to pick up
  • Triage task assigns to existing issue flow or creates new issues

Acceptance

  • Periodic task connects to at least one relay and pulls new mentions
  • Events are deduplicated by event id
  • Output is a scored JSONL file, not a raw firehose

Dependencies

  • Needs Timmy's npub configured (or derive from nsec if available)
## Source Sovereign Developer's Brief (2026-03-27), Section 4 "Low-Hanging Fruit", item 2. ## What Implement a Huey task that filters incoming Nostr mentions (NIP-01 kind:1 events mentioning Timmy's npub) into a priority queue. ## Design - Subscribe to Nostr relay websocket for mentions - Score events by: known npub (high), reply vs. fresh mention, keyword relevance - Write scored events to `~/.timmy/nostr/inbox.jsonl` for the triage task to pick up - Triage task assigns to existing issue flow or creates new issues ## Acceptance - Periodic task connects to at least one relay and pulls new mentions - Events are deduplicated by event id - Output is a scored JSONL file, not a raw firehose ## Dependencies - Needs Timmy's npub configured (or derive from nsec if available)
Timmy was assigned by Rockachopa 2026-03-28 03:52:19 +00:00
Timmy commented 2026-03-28 04:45:19 +00:00
Owner
Copy Link

Closing as duplicate during backlog burn-down. Canonical issue: #32.

Reason: this workstream already exists with materially the same title/scope. Keeping one canonical thread prevents agent churn and review waste.

Closing as duplicate during backlog burn-down. Canonical issue: #32. Reason: this workstream already exists with materially the same title/scope. Keeping one canonical thread prevents agent churn and review waste.
Timmy closed this issue 2026-03-28 04:45:19 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
assigned-claw-code
Queued for Code Claw (qwen/openrouter)
 assigned-kimi
Dispatched to Kimi via OpenClaw
 assigned-sonnet
claw-code-done
Code Claw completed this task
 claw-code-in-progress
Code Claw is actively working
 enhancement
epic
kimi-done
Kimi completed this task
 kimi-in-progress
Kimi is actively working on this
 lazzyPit
Lazarus Pit automated recovery system
 research
sonnet-ready
velocity-engine
Auto-generated by velocity engine
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
KimiClaw Rockachopa Timmy allegro antigravity bezalel claude claw-code codex-agent ezra gemini google grok groq hermes kimi manus perplexity sonnet
No Assignees Timmy
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/timmy-config#33
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?