2025-09-21 - 2026-09-21
Overview
1 Release published by 1 user
Published
v1.0.0
Rendezvous v1.0.0
22 Issues closed from 1 user
Closed
#25 Build a thin interactive Rendezvous test client
Closed
#20 Publish TestClient workflows, integration guides, and operator runbooks
Closed
#19 Version and publish the Client/Contracts packages and server artifacts
Closed
#18 Establish capacity, soak, resilience, and availability topology gates
Closed
#17 Containerize and document secure Linux deployment
Closed
#16 Add privacy-safe observability, health, audit, and operator controls
Closed
#15 Harden tenant isolation, rate limits, replay defense, parsers, and overload behavior
Closed
#14 Build the deterministic three-party and NAT-topology integration harness
Closed
#13 Standardize typed connection outcomes, retries, reporting, and fallback handoff
Closed
#12 Implement caller-owned LiteNetLib punch and direct-connect coordination in the SDK
Closed
#11 Implement authenticated host presence and an amplification-safe LiteNetLib NAT mediator
Closed
#9 Build the publisher and session-browser .NET client SDK
Closed
#8 Implement bounded compatible-session browsing and listing visibility
Closed
#7 Implement session registration, UDP-presence-gated leases, and expiry
Closed
#6 Build atomic ephemeral state and define single-active availability semantics
Closed
#4 Define versioned v1 HTTP, UDP, error, and compatibility contracts
Closed
#5 Implement game/environment provisioning, principals, and signing-key lifecycle
Closed
#2 Ratify the v1 architecture, trust model, and privacy threat model
Closed
#3 Bootstrap the .NET solution and continuous quality gates
Closed
#27 Add read-only diagnostic and Grafana dashboards
Closed
#26 Stream live session-list updates to server browsers
Closed
#10 Implement short-lived join attempts, punch capabilities, and connection tickets
36 Issues created by 1 user
Opened
#1 Roadmap: ship the Rendezvous connection control plane
Opened
#2 Ratify the v1 architecture, trust model, and privacy threat model
Opened
#3 Bootstrap the .NET solution and continuous quality gates
Opened
#4 Define versioned v1 HTTP, UDP, error, and compatibility contracts
Opened
#5 Implement game/environment provisioning, principals, and signing-key lifecycle
Opened
#6 Build atomic ephemeral state and define single-active availability semantics
Opened
#7 Implement session registration, UDP-presence-gated leases, and expiry
Opened
#8 Implement bounded compatible-session browsing and listing visibility
Opened
#9 Build the publisher and session-browser .NET client SDK
Opened
#10 Implement short-lived join attempts, punch capabilities, and connection tickets
Opened
#11 Implement authenticated host presence and an amplification-safe LiteNetLib NAT mediator
Opened
#12 Implement caller-owned LiteNetLib punch and direct-connect coordination in the SDK
Opened
#13 Standardize typed connection outcomes, retries, reporting, and fallback handoff
Opened
#14 Build the deterministic three-party and NAT-topology integration harness
Opened
#15 Harden tenant isolation, rate limits, replay defense, parsers, and overload behavior
Opened
#16 Add privacy-safe observability, health, audit, and operator controls
Opened
#17 Containerize and document secure Linux deployment
Opened
#18 Establish capacity, soak, resilience, and availability topology gates
Opened
#19 Version and publish the Client/Contracts packages and server artifacts
Opened
#20 Publish TestClient workflows, integration guides, and operator runbooks
Opened
#21 Pilot SpaceGame against Rendezvous v1
Opened
#22 Pilot Unscouted against Rendezvous v1
Opened
#23 Run the real-network canary and declare Rendezvous v1 production-ready
Opened
#24 Design an optional relay fallback from measured v1 traversal failures
Opened
#25 Build a thin interactive Rendezvous test client
Opened
#26 Stream live session-list updates to server browsers
Opened
#27 Add read-only diagnostic and Grafana dashboards
Opened
#28 Design shared state and deterministic routing for HA and multi-region
Opened
#29 Scale beyond the measured single-active v1 capacity envelope
Opened
#30 Add platform authentication adapters without making Rendezvous an identity provider
Opened
#31 Introduce dual-stack endpoint candidates with IPv6-preferred traversal
Opened
#32 Provide a longer-lived dedicated-server credential kind or server-driven refresh
Opened
#33 Frozen-envelope UDP path exceeds the documented amplification budget; telemetry records a constant
Opened
#34 Document and mitigate IP-scoped anonymous join-attempt idempotency under CGNAT
Opened
#35 Scope per-principal listing quotas and revocation to game/environment tenants
Opened
#36 Enforce or retire the service-side one-time connection-ticket consumption invariant