privacy: avoid exposing private RF propagation coordinates through overlay georeferencing

Abierto
  • ¿Algo no está bien?
#245 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
12/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
python
Área
backend, security

Línea de trabajo

Start with docs/features/rf_propagation/README.md and the rf_propagation_recompute view in nodes/views.py, then trace rf_propagation/tasks.py to see which coordinates reach the render and which bounds reach the API response. This is a privacy design task, so the first step is agreeing on a precision model for public bounds, not writing code. Done means a documented model, response tests for private-coordinate renders, and an overlay that still aligns usefully on the map.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Context

The RF propagation feature lets a radio node owner provide private, true coordinates for their node so the backend can render an accurate RF coverage map. The UI then overlays the generated PNG on a normal geographic map using the exact georeferenced bounds returned by the API.

This is related to the frontend alignment bug tracked in pskillen/meshtastic-bot-ui#204. While investigating that, we need to make sure any eventual alignment fix does not accidentally reveal the private transmitter coordinates.

Privacy concern

Today the render pipeline needs the true coordinates to calculate the correct RF map. Even if the PNG itself is low resolution, the API-provided overlay bounds and image placement may allow a client to infer the true transmitter location more precisely than intended, especially if the coverage pattern has a visible origin or if repeated renders can be compared.

The intended UX is that the public map should show a useful RF propagation approximation without betraying private node coordinates.

Possible approaches to investigate

  • Render with true coordinates, then post-process the PNG and georeferencing before exposing it.
  • Snap the exposed overlay anchor/bounds to a lower precision grid, then crop/pad/translate the raster so the visual alignment remains useful without exposing the private origin.
  • Add a privacy-preserving response contract, e.g. public display bounds that differ from internal render bounds, with documented precision guarantees.
  • Consider whether the origin-like visual features in the PNG itself need masking, blurring, cropping, or a minimum output resolution.
  • Ensure cache keys, filenames, metadata, logs, and API responses do not leak private coordinates directly or via overly precise georeferencing.

Acceptance criteria

  • The backend has a documented privacy model for RF renders based on private node coordinates.
  • API responses for RF propagation do not expose true private coordinates or exact private-coordinate-derived bounds beyond an agreed precision.
  • The frontend can still place the overlay accurately enough for the feature to be useful.
  • Existing and new renders remain cacheable without leaking private coordinate data via public identifiers or metadata.
  • Tests cover the public response contract for private-coordinate renders.

Notes

Current docs: docs/features/rf_propagation/README.md.
Relevant implementation areas likely include nodes/views.py::rf_propagation_recompute, rf_propagation/tasks.py, payload/hash generation, and render model serialization.

Lenguaje dominante
Python
Estrellas
1
Forks
0
Merge medio
23 h 9 min
PR fusionados (30 d)
15

Preparar el entorno

  • Incluye un Dockerfile o un archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de pskillen/meshflow-api

Todos los issues de pskillen/meshflow-api

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.