POINT Protocol¶

Passive Observation and Identification of Network Telemetry

What is POINT?¶

POINT is a NeXuS security principle for evaluating any software, widget, service, or system component that initiates outbound network connections — scheduled or otherwise.

The core question is simple:

If it talks out, it talks about you.

Consider this: a weather widget needs to know your location to show you local conditions. It determines that location one of two ways — you tell it, or it figures it out from your IP address.

Most widgets use your IP. They send a request to a server. That server performs IP geolocation — a lookup that maps your IP to a city, region, and country. It then returns weather for that location. Convenient. Accurate. And a complete de-anonymization event every 30 minutes.

Here is what that silent background request actually reveals:

Your real IP address — or your VPN/proxy exit node, which narrows the field significantly
Your approximate physical location — city-level accuracy is standard, sometimes street-level
That you are online and active — the request cadence maps your session activity
What software you are running — the User-Agent string in the request identifies your desktop environment and widget version
A consistent identity anchor — the same IP, same schedule, same fingerprint, day after day

Now imagine you are using Tor or a VPN. You believe you are anonymous. But your weather widget is making a direct clearnet request — bypassing your privacy stack entirely — because nobody told it to go through Tor. The weather server logs your exit IP. If that exit IP is consistent across sessions, you have just created a persistent pseudonymous identity that an observer can track over time.

Worse: if your VPN ever drops for a moment and the widget fires during that window, it just sent your real IP to a third-party logging server on a schedule. That is called a correlation attack surface — and you handed it over for a temperature reading.

A weather widget that polls wttr.in every 30 minutes isn't just fetching temperature. It is broadcasting:

Your IP address (or exit node)
Your geographic region via IP geolocation
Your system uptime and active session patterns
Your desktop configuration via User-Agent
A consistent, repeatable fingerprint across time

Individually these seem harmless. Collectively they are a POINT of identification.

The POINT Test¶

Before adding any component that makes network requests, ask:

Question	Why it matters
Who receives the request?	Third-party = third-party knowledge of your existence
How often does it call out?	Cadence is a fingerprint — regular intervals are trackable
Is the destination logged?	Most public APIs log IPs by default
Can it be routed?	If not Tor/I2P-capable, it leaks your real or VPN exit IP
Is it necessary?	Convenience features are rarely worth the exposure

If any answer raises concern — remove it or route it.

Common POINT Violations on the Desktop¶

These are everyday components that silently create network telemetry:

Weather widgets — poll external APIs on a schedule, IP-logged
NTP time sync — leaks existence and timezone to time servers
Update notifiers — phone home with package lists and versions
Crash reporters — send system info and stack traces to vendors
Font/icon CDNs — web apps loading remote fonts expose your browser
Thumbnail fetchers — media players fetching album art, movie posters
DNS resolvers — every lookup is a record of what you accessed
Telemetry daemons — systemd-resolved, GNOME Software, KDE Discover

POINT and the NeXuS Desktop¶

The NeXuS desktop is built on the principle that the desktop itself should generate zero unsolicited outbound traffic.

Every outbound connection should be:

Intentional — initiated by the user, not background daemons
Routed — passing through Medusa/Tor/I2P where possible
Auditable — visible in OpenSnitch or equivalent
Necessary — if it can be removed without loss of function, remove it

The weather widget was removed from the NeXuS panel for this reason. The clock reads local system time. The panel has no network dependencies.

POINT and Sovereign Infrastructure¶

When NeXuS nodes communicate with each other, they do so through:

I2P — for persistent, pseudonymous node identity
Tor — for ephemeral, unlinkable connections
Medusa — the NeXuS proxy layer enforcing routing policy
DIVA — distributed ledger that never touches the clearnet (built by Konrad, AGPLv3 — thank you, Konrad)

This means NeXuS infrastructure itself is POINT-compliant by architecture — not by policy, not by trust, but by design. There is no clearnet surface to observe.

POINT vs Convenience¶

The tension is real. Weather, time sync, package updates, and crash reports exist because they are useful. The NeXuS answer is not to eliminate utility but to route it:

Time sync → chrony with NTS over Tor (already deployed)
Package updates → manual, user-initiated, through Medusa
Crash reports → disabled at the package/config level
Any external data → fetched on demand, not on schedule

Summary¶

Every scheduled outbound call is a heartbeat. Heartbeats can be heard. NeXuS does not broadcast a heartbeat.

POINT is not paranoia. It is the recognition that passive observation is the most common form of surveillance — and the most easily prevented.

NeXuS — Sane • Simple • Secure • Stealthy • Beautiful