multi-region, bake in lat/long to fixed-region conn blobs, have clients search nearby regions?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7.5k
- Forks
- 311
- Avg merge
- 7h 7m
- Merged PRs (30d)
- 59
Description
To improve robustness of static connection tokens, perhaps they should optionally include the derp region's lat/long too, and then if the DERP map changes over time, the client can try the nearest two (Haversine distance probably good enough) to look for the server's public key again
And/or maybe the server should be able to register at two DERP regions.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by tracing static connection-token handling and DERP map usage, then clarify whether nearby-region lookup, dual DERP registration, or both are in scope. Done should be a decided, testable design with clear behavior for changing DERP maps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100