mirror of
https://relay.ngit.dev/npub15qydau2hjma6ngxkl2cyar74wzyjshvl65za5k5rl69264ar2exs5cyejr/ngit-grasp.git
synced 2026-10-05 15:08:24 +00:00
issue: complete phase 0 - all research finished
This commit is contained in:
@@ -470,3 +470,24 @@ The current phased roadmap above is **SUPERSEDED** pending proper planning:
|
||||
- `docs/research/pyramid-style-queries-design.md` - Feasibility analysis for rust-nostr
|
||||
- **Next:** Update strategy document to reflect HTTP-based approach for queries
|
||||
- Phase 0 research complete, ready to finalize architecture and proceed to Phase 1
|
||||
|
||||
### 2026-01-15 [Session 11:38]
|
||||
- **Final Phase 0 research:** Explored forking rust-nostr to support pyramid-style queries
|
||||
- Comprehensive analysis of what it would take to modify nostr-relay-builder
|
||||
- Key findings:
|
||||
- Implementation effort: 5-7 days (vs 1-2 days for HTTP NIP-86)
|
||||
- Ongoing maintenance: 18-29 hours/month (vs 1-2 hours/month for HTTP)
|
||||
- rust-nostr is extremely active: 305 commits in 15 days (~20/day)
|
||||
- Breaking changes in ~50% of releases
|
||||
- Pyramid uses khatru framework (Go), NOT nostr-relay-builder
|
||||
- Upstream acceptance likelihood: Low (10-20%)
|
||||
- **Final decision confirmed: HTTP-based NIP-86 is the correct approach**
|
||||
- No fork needed
|
||||
- Standards-compliant
|
||||
- Minimal maintenance burden
|
||||
- Achieves same functional goals
|
||||
- Deliverable committed:
|
||||
- `docs/research/rust-nostr-fork-analysis.md` - Complete fork analysis (1,316 lines)
|
||||
- **Phase 0 research COMPLETE** ✅
|
||||
- All 4 research documents committed and ready for review
|
||||
- Ready to update strategy document and begin Phase 1 implementation
|
||||
|
||||
Reference in New Issue
Block a user