Skip to content

Fix explorer globe play markers using COBE native colors#168

Merged
raymondjacobson merged 8 commits intomainfrom
fix/globe-play-markers
Mar 31, 2026
Merged

Fix explorer globe play markers using COBE native colors#168
raymondjacobson merged 8 commits intomainfrom
fix/globe-play-markers

Conversation

@raymondjacobson
Copy link
Copy Markdown
Contributor

@raymondjacobson raymondjacobson commented Mar 28, 2026

Summary

  • Drop the 2D overlay canvas + custom projection for play markers entirely
  • Use COBE 2.0's per-marker color property to render purple play dots directly through WebGL — guaranteed correct positioning
  • Purple (#c084fc) → white color fade with playglobe-style scale-up/scale-down animation
  • Fix play.lat && play.lng check that dropped plays at lat=0/lng=0
  • Match playglobe's marker size randomization (0.06 + random * 0.04)
  • Globe panel uses min-h-[500px] + items-stretch to match Transaction Analytics height
  • Add / keyboard shortcut to focus search input

Test plan

  • Verify play dots appear in correct locations on the globe
  • Verify play dots are purple and fade to white
  • Verify globe panel height matches Transaction Analytics panel
  • Press / to focus search bar

🤖 Generated with Claude Code

raymondjacobson and others added 6 commits March 30, 2026 16:21
…nvas

Drop the 2D overlay canvas and custom projection entirely. COBE 2.0
supports per-marker colors via marker.color, so play markers now render
through COBE's own WebGL pipeline — guaranteed correct positioning.
Purple (#c084fc) fading to white with playglobe-style scale animation.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Log at Info level when cache goroutines start and when refreshes
succeed, to diagnose why validator locations cache produces no output.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The console was using zap.NewNop() which discards ALL log output,
making it impossible to diagnose cache issues. All cache loggers
are derived from the console logger, so they were also silent.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The explorer was dropping most plays because it required exact
city+state+country matches in the location DB. Now falls back to
country-level coordinates (with jitter) when city lookup fails,
matching the playglobe's approach of showing every play.

Also increased PLAY_DECAY_MS from 1s to 8s to match the playglobe.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The /version endpoint now checks for OPENAUDIO_LATITUDE and
OPENAUDIO_LONGITUDE env vars before falling back to ipinfo.io.
Each devnet node gets a distinct simulated city:
  node1: New York, node2: London, node3: Tokyo, node4: Sydney

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@raymondjacobson raymondjacobson force-pushed the fix/globe-play-markers branch from 0dd638f to afa9fcf Compare March 30, 2026 23:22
…ations

The console caches (dashboard + validator locations) were only started in
Run() which is never called from main.go — only Initialize() is. Moved
cache startup goroutines into Initialize() with ETL DB readiness polling.

Also: faster proposal lasers (800ms), smaller play dots, instant pop-in
with fade-out, and 4s decay. Added error logging for /version fetches.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@raymondjacobson raymondjacobson changed the title Fix globe play markers using COBE native colors Fix explorer globe play markers using COBE native colors Mar 31, 2026
@raymondjacobson raymondjacobson merged commit 77b468f into main Mar 31, 2026
3 checks passed
@raymondjacobson raymondjacobson deleted the fix/globe-play-markers branch March 31, 2026 00:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant