MESH//GANGSSeason 2
MESHGANGS 2.1 — TERRITORY AND REPEATERS PUBLIC ATTRIBUTION
Front, defence, HQ raid, and region-control records may publicly link a handle or gang to resolution-8 districts and a time rounded down to 15 minutes.
For 30 days, fronts and defences may show the credited handle, gangs, public H3 cells, coalesced area gained, and rounded time. Hidden operators become “redacted operator.” After 30 days, cell-level events are deleted; only weekly aggregates, ranks, and earned cosmetics remain.
A public radio pulse contains only a gang, opaque zone identifier, traffic class, score delta, a deterministic generalized point inside the public zone, and time rounded down to 15 minutes. It never returns the receiver H3 cell or names an operator, device, packet, origin, exact reception time, exact GPS, or trail, and it expires after seven days. Ownership-transition H3 cells remain public because the territory itself is public.
A Flashpoint publishes its seven public target districts, curated region, frozen gang entrants, aggregate gang points, rank, scoring-day count, direct target-cell count, countdown, result, and earned crew cosmetic. It never publishes a contributing operator, route, receiver position, GPS, trail, device, packet digest, or origin. Flashpoint points are a separate weekly aggregate and cannot change normal territory or RF standings.
Season 2 begins on a neutral resolution-8 map. Public maps may show contiguous gang contours, charging haze, generalized network-mix buckets, normalized strength, fading state, fronts, public owned H3 cells, a gang HQ, regional control, and a FORTIFIED badge. They never reveal a member's private home region, exact receiver/core position, or exact siege-start time.
Optional activity and infrastructure overlays distinguish MeshCore and Meshtastic only as generalized diagnostics. Turf is always gang-coloured. Meshtastic infrastructure appears only as a generalized H3 cell with no node identity; MeshCore public signed repeaters may retain their published exact position.
Received MeshCore or Meshtastic packet bytes exist only long enough in client memory to classify and hash them. Meshtastic NodeInfo/Position is reduced locally to a one-way identity token, role, and generalized H3 cell; coordinates and payload bytes are discarded immediately. Collection is live-only, with no disk queue or saved trail.
The PWA uses a wake lock but pauses when hidden. Android uses a visible location + connected-device foreground service for screen-off Patrol and does not request permanent background location. Self-tests verify BLE, precise GPS, and server reachability without creating an Observation or influence.
Signed MeshCore MQTT adverts may validate public repeater identity, location, and freshness, but external data cannot create an Observation, score, field, claim, or capture. Meshtastic MQTT/API traffic is ignored entirely for gameplay. Infrastructure control requires duplicate-bounded local RF evidence, two separated epochs, stability, freshness, a recent direct gang anchor, and a strict lead.
Public serializers never expose Meshtastic node identity, radio address, coordinates, local reception time, observer, or exact receiving cell. MeshGangs is independently compatible with Meshtastic and is not affiliated with or endorsed by the Meshtastic project.
Ordinary packet metadata, public radio pulses, and peppered repeater fingerprints are kept seven days. Quarantined metadata is kept 30 days. Exact phone GPS is scrubbed within 24 hours. Sanitized repeater registry metadata remains while useful for the public network map. Signed-in players may report profiles, gangs, recruiting listings, or battle events for audited operator review.
The dark-styled map requests standard tiles from OpenStreetMap. OpenStreetMap receives tile coordinates and ordinary network information such as your IP address; MeshGangs sends it no account, device, observation, or patrol data.
The anonymous radio test performs BLE, GPS, and server checks locally, then records only a rate-limited pass or categorical failure count. It rejects coordinates, packet data, and device identifiers and cannot create an account, Observation, or influence.
Notifications are off until enabled in Settings. Web Push endpoint and browser key material are encrypted at rest; the push provider receives encrypted delivery metadata needed to deliver the alert. Android uses a device-local best-effort HTTPS check instead of Firebase. Opted-in lock screens may show a public curated region name, but never an H3 cell, GPS, device, packet, or observer. Quiet-hour suppression leaves the event available in the private in-site inbox.