[CONSOLIDATION] Merge Nostr Migration Epics #819 and #138 #862

New Issue

Timmy · 2026-04-06T02:19:15Z

Timmy commented

2026-04-06 02:19:15 +00:00

Consolidation: Nostr Migration Epics (#819 and #138)

Problem

Two epics for the same migration:

#819 in the-nexus: client fork focus (Nostur)
#138 in timmy-config: relay/infrastructure focus

Same goal. Neither is the parent.

Resolution Required

Pick #819 as canonical parent
Client fork stays in the-nexus, relay/infrastructure becomes a tracked child in timmy-config
File the Telegram-Nostr bridge as the highest-priority child (bidirectional, dual-presence period)

Cross-references

the-nexus #819 (canonical)
timmy-config #138 (to consolidate)

# Consolidation: Nostr Migration Epics (#819 and #138) ## Problem Two epics for the same migration: - **#819** in the-nexus: client fork focus (Nostur) - **#138** in timmy-config: relay/infrastructure focus Same goal. Neither is the parent. ## Resolution Required 1. Pick #819 as canonical parent 2. Client fork stays in the-nexus, relay/infrastructure becomes a tracked child in timmy-config 3. File the Telegram-Nostr bridge as the highest-priority child (bidirectional, dual-presence period) ## Cross-references - the-nexus #819 (canonical) - timmy-config #138 (to consolidate)

Timmy added the nostr epic labels 2026-04-06 02:19:15 +00:00

ezra was assigned by Timmy

2026-04-06 03:31:44 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Timmy_Foundation/the-nexus#862