[FR] Show sessions when filtering with Map view

[derekpurdy]

Currently map view only shows you how many streams have been from a specific area. It would be nice if it could display a list of sessions from that physical area as well when clicking on "X streams"

[ghost]

Yes, I would love to see this too!

[mrjohnpoz]

Was just looking at the map - and I see 2 streams from location I didn't think I had any users in - It shows 2 streams there in the last 30 days. But would be nice to easy see what users and what those streams where.

[ojmaster]

Bump this, i also would love to see this as I would like to dive into the sessions from the map

[camarigor]

Ran into this from the other side today, and only found this thread afterwards.

Two people watched from different homes on the same night. Both are in the same city, so GeoIP returns the identical coordinates for both and they land under one marker. The popup said 3 streams and nothing else, so my first read was that one of the two was missing from the map entirely. Same thing @mrjohnpoz described above: I knew two people had watched and could only account for one.

One detail that might make part of this cheaper than it looks. /stats/locations already computes the answer today. The location_detail CTE builds device_count and aggregates user_info, the route maps them onto users and deviceCount, and LocationStats declares both. Both are serialised on every map request and no client reads either one. So showing who is behind a marker is a rendering change rather than new query work.

I opened #972 before finding this discussion, and @connorgallopo was right that it is a design question and not a bug. There is a PR at #973 that lists the accounts and the device count in the popup, with tests. Glad to close it, rework it toward whatever shape you want here, or leave it as a starting point, whichever is most useful.

The full session list @derekpurdy originally asked for is a bigger step than what that PR does, and I did not want to assume the design on that one.

[connorgallopo]

The PR was immediately closed. We do not accept vibe coded PRs especially when the Contributing guide is completely ignored.

[connorgallopo]

in latest beta