Feedback request: map-first community safety updates—what would you add/remove? 

Hey PH 👋 — I’m building Ice Watch, a community safety network that defaults to a sector map showing verified activity in real time (map-first, quick signal, less noise). 

I’d love feedback from builders + community folks on a few product decisions:

1. Verification: What should qualify as “verified” in a community-driven feed? (e.g., multiple independent reports, trusted contributors, time/geo consistency, moderator review)

2. False positives: What’s the best UX for “unverified / pending / disputed” without hiding important info?

3. Privacy & safety: What location granularity feels responsible (exact point vs. block vs. sector), and what anti-abuse controls would you expect?

4. MVP focus: If you had to keep only 3 things for v1 of a safety map, what are they?

If you’re open to it, reply with:

• your use case (neighborhood group / venue owner / parent / etc.)

• what you’d trust as a verification signal

• one feature you’d want day-1

App link: icestorm.site