next.orly.dev

600 Commits

4 Branches

314 Tags

32 MiB

Tree: 9e0e9d82f4

Commit Graph

Author	SHA1	Message	Date
woikos	1711345c64	Fix NIP-77 negentropy server-side event pushing (v0.55.7) - Add have_ids, need_ids, complete fields to NegOpenResponse proto - Fix ID encoding in server: decode hex strings to binary before sending - Fix event sending order: send NEG-MSG response before EVENT envelopes - Client now waits for expected events after reconciliation completes - Store received events from peer in sync client message loop This enables bidirectional event sync via NIP-77 negentropy. The server can now push events it has that the client needs, in addition to the client pushing events to the server. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>	4 months ago
woikos	c8dbf62a44	Increase negentropy sync limit from 100k to 1M events (v0.55.5) - Add MaxEvents config option to negentropy manager - Increase default sync limit from 100,000 to 1,000,000 events - Ensures full database sync for relays with 200k+ events Files modified: - pkg/sync/negentropy/manager.go: Add MaxEvents config, use configurable limit - pkg/sync/negentropy/server/service.go: Increase hardcoded limit to 1M Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>	4 months ago
woikos	769f9d2daa	Add IPC sync services and NIP-77 negentropy synchronization (v0.55.0) - Add four independent gRPC sync service binaries: - orly-sync-distributed: Serial-based peer-to-peer sync - orly-sync-cluster: Cluster replication with persistent state - orly-sync-relaygroup: Relay group config discovery (Kind 39105) - orly-sync-negentropy: NIP-77 efficient set reconciliation - Implement NIP-77 negentropy protocol for relay-to-relay sync - Add push-based event transfer for negentropy sync - Add client-facing NIP-77 WebSocket support (NEG-OPEN/MSG/CLOSE) - Add deployment scripts with symlink-based versioning - Add Makefile targets for quick deployment and rollback - Refactor existing sync code into modular service packages - Add proto definitions for all sync services - Integrate negentropy service into orly-launcher supervisor - Advertise NIP-77 support in relay info document Files modified: - Makefile: Add sync service build targets and deployment commands - README.md: Document NIP-77 support - app/config/config.go: Add negentropy configuration options - app/handle-message.go: Route NEG-* envelopes to negentropy handler - app/handle-negentropy.go: New file for NIP-77 WebSocket handling - app/handle-relayinfo.go: Advertise NIP-77 support - cmd/orly-launcher/: Add negentropy service management - cmd/orly-sync-/: New service binaries - main.go: Add negentropy gRPC client initialization - pkg/proto/orlysync/: New proto definitions and generated code - pkg/sync//: Refactored sync packages with gRPC services - scripts/deploy-orly.sh: New symlink-based deployment script - scripts/build-and-deploy.sh: New build and deploy workflow Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>	4 months ago

Author

SHA1

Message

Date

woikos

1711345c64

Fix NIP-77 negentropy server-side event pushing (v0.55.7)

- Add have_ids, need_ids, complete fields to NegOpenResponse proto
- Fix ID encoding in server: decode hex strings to binary before sending
- Fix event sending order: send NEG-MSG response before EVENT envelopes
- Client now waits for expected events after reconciliation completes
- Store received events from peer in sync client message loop

This enables bidirectional event sync via NIP-77 negentropy. The server
can now push events it has that the client needs, in addition to the
client pushing events to the server.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

4 months ago

woikos

c8dbf62a44

Increase negentropy sync limit from 100k to 1M events (v0.55.5)

- Add MaxEvents config option to negentropy manager
- Increase default sync limit from 100,000 to 1,000,000 events
- Ensures full database sync for relays with 200k+ events

Files modified:
- pkg/sync/negentropy/manager.go: Add MaxEvents config, use configurable limit
- pkg/sync/negentropy/server/service.go: Increase hardcoded limit to 1M

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

4 months ago

woikos

769f9d2daa

Add IPC sync services and NIP-77 negentropy synchronization (v0.55.0)

- Add four independent gRPC sync service binaries:
  - orly-sync-distributed: Serial-based peer-to-peer sync
  - orly-sync-cluster: Cluster replication with persistent state
  - orly-sync-relaygroup: Relay group config discovery (Kind 39105)
  - orly-sync-negentropy: NIP-77 efficient set reconciliation
- Implement NIP-77 negentropy protocol for relay-to-relay sync
- Add push-based event transfer for negentropy sync
- Add client-facing NIP-77 WebSocket support (NEG-OPEN/MSG/CLOSE)
- Add deployment scripts with symlink-based versioning
- Add Makefile targets for quick deployment and rollback
- Refactor existing sync code into modular service packages
- Add proto definitions for all sync services
- Integrate negentropy service into orly-launcher supervisor
- Advertise NIP-77 support in relay info document

Files modified:
- Makefile: Add sync service build targets and deployment commands
- README.md: Document NIP-77 support
- app/config/config.go: Add negentropy configuration options
- app/handle-message.go: Route NEG-* envelopes to negentropy handler
- app/handle-negentropy.go: New file for NIP-77 WebSocket handling
- app/handle-relayinfo.go: Advertise NIP-77 support
- cmd/orly-launcher/: Add negentropy service management
- cmd/orly-sync-*/: New service binaries
- main.go: Add negentropy gRPC client initialization
- pkg/proto/orlysync/: New proto definitions and generated code
- pkg/sync/*/: Refactored sync packages with gRPC services
- scripts/deploy-orly.sh: New symlink-based deployment script
- scripts/build-and-deploy.sh: New build and deploy workflow

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

4 months ago

3 Commits (9e0e9d82f405220fefc839ee8976ff5144bfbd25)