MrAlders0n 689bc2326a fix(ingest): clear a node's location on an explicit 0/0 advert ...

A repeater that advertises 0/0 is hiding its position. It was stored as a literal 0/0 that every consumer had to special-case; now the stored latitude, longitude and location source are cleared, an omitted location still preserves the stored one, and the nodeUpdate event sends explicit null lat/lng so clients can clear too. Migration 043 drops rows stored as 0/0 before this change.

2026-09-30 11:29:01 -04:00

..

mock

perf(db): compute route ambiguity once per reconfirm run

2026-09-30 10:31:08 -04:00

db.go

ingestion + ws complete

2026-05-22 11:43:27 -07:00

models.go

feat(scopes): import cached regional MeshMapper catalogues

2026-09-30 07:19:03 -04:00

observer_comparison.sql.go

feat(stats): compare flood packets reported by two observers (#152)

2026-09-19 10:36:39 -04:00

paths.sql.go

feat(stats): add bounded path and hash-width analytics (#159)

2026-09-23 20:18:41 -04:00

querier.go

perf(db): compute route ambiguity once per reconfirm run

2026-09-30 10:31:08 -04:00

queries.sql.go

fix(ingest): clear a node's location on an explicit 0/0 advert

2026-09-30 11:29:01 -04:00

route_evidence.sql.go

fix: address maintainer review for #172

2026-09-30 07:19:03 -04:00

signal.sql.go

feat(stats): add bounded reception signal analytics (#157)

2026-09-23 20:16:22 -04:00