Release 7b · Queued
Grouped Pins
Network-aware map clustering. When multiple people you follow have independently pinned the same spot, they surface as a single grouped place.
Summary
The map-level experience of overlapping pins from your network. When multiple people you follow have pinned the same spot — independently, without any social connection at pin-creation time — the map surfaces it as a single grouped place with stacked avatars and a combined timeline.
This is Scenario F from SCOPE.md: two users independently pin the same spot, proximity detection finds the overlap, they later follow each other, and the connection surfaces on the next map load automatically — no migration, no backfill.
What's in scope
- Proximity detection for independent overlap (Scenario F)
- Smart pin grouping on map — enhanced Mapbox clustering with network awareness (grouped only if the pins are from your network, not strangers)
- Amalgamated place card — stacked avatars, combined visit timeline from all networked pinners
- AI-generated display name for grouped pins (where underlying pins have different titles)
Architecture
No
places entity. The map queries all pins from the user's network and clusters them via PostGIS ST_ClusterDBSCAN. Cluster results are a view, not stored state. Retroactive connections surface automatically on the next map load — no migration, no backfill.
Open questions
- Proximity threshold — SCOPE.md starts at ~500m for grouped pins. Too loose in dense urban areas, too tight in open desert. Category-aware or terrain-aware adaptation?
- Display name generation — client-side or Edge Function? Same question as R2. Answer consistently.
- Privacy of grouped pins — if one user has the pin private and one shared, does the group respect the stricter setting?