Per-User Location Hotspots

systems/user-hotspots.md · System · personalization, geo, privacy, digest, livemusictonight

unverified: no trust signals recorded yet

A derived projection of a signed-in user's primary/secondary location centroids (home/work) from their own signals, used to personalize near-me defaults, reminders, and the Digest.

Per-User Location Hotspots

includes/user-hotspots.php derives a signed-in user's primary and secondary location centroids (usually home and work) plus a typical radius, from the user's OWN signals. It is a derived projection cached in user_hotspots (migration sprint_user_hotspots.sql), recomputed lazily — never a track log.

How it works

• Signals (userHotspotPoints): check-ins (weight 3, the strongest "you were here"),

where the user searched on Live Music Tonight (lmt_interest area coords), and the coords of businesses they saved (lb_follows).

• Derivation (userComputeHotspots): grid-bucket points at ~10 miles, rank by density,

take the top one or two clusters (the second only if >=15mi from the first) as centroids; the typical radius is the 75th-percentile spread, snapped to 5/10/25/50/100.

• Read (userGetHotspots): returns the cached row, recomputing if older than 7 days or

missing. userForgetHotspots clears it; userHotspotLabel names the nearest city.

What it powers

• Near-me defaults — when a signed-in visitor has no live location (geolocation denied,

no Cloudflare geo header), LMT centers on the home hotspot and defaults the radius to the user's typical distance. Precise geolocation still wins.

• my.doozer.cloud "Your spots" — shown in plain language with a Forget control.
• Future: reminder targeting (an interested artist returning within the user's radius) and

Digest "near your home / near your work" blocks.

Guardrail

Signed-in only; derived from the user's own usage; coarse (centroids + radius, not a path); visible and clearable on my.doozer.cloud. A convenience that remembers where you are, not surveillance. See no dark patterns.