Can't disable telemetry

[fizitzfux]

Source

AUR

App logs

07:50:10 [info:albert.apps] Indexed 148 applications [39 ms]
07:50:10 [warn:albert.apps] No terminal configured. Using WezTerm.
07:51:10 [debg:albert] trySendReport {
    "data": {
    },
    "id": "d5e4777a",
    "report": 2,
    "time": "2024-12-05T07:51:10+00:00"
}

07:52:10 [debg:albert] trySendReport {
    "data": {
    },
    "id": "d5e4777a",
    "report": 2,
    "time": "2024-12-05T07:52:10+00:00"
}

07:52:10 [warn:albert] Failed to send telemetry data:
07:52:10 [warn:albert] Socket operation timed out
07:52:10 [warn:albert]
07:52:10 [warn:albert] Failed to send telemetry data:
07:52:10 [warn:albert] Socket operation timed out
07:52:10 [warn:albert]
07:53:10 [debg:albert] trySendReport {
    "data": {
    },
    "id": "d5e4777a",
    "report": 2,
    "time": "2024-12-05T07:53:10+00:00"
}

07:53:10 [warn:albert] Failed to send telemetry data:
07:53:10 [warn:albert] Socket operation timed out
07:53:10 [warn:albert]
07:54:10 [debg:albert] trySendReport {
    "data": {
    },
    "id": "d5e4777a",
    "report": 2,
    "time": "2024-12-05T07:54:10+00:00"
}

07:54:10 [warn:albert] Failed to send telemetry data:
07:54:10 [warn:albert] Socket operation timed out
07:54:10 [warn:albert]

Current Behavior

Since the latest release, v0.26.9, Albert keeps attempting to send telemetry. This is not expected behavior as telemetry is disabled in the settings.
Toggling telemetry on and off again and rebooting doesn't fix this.

Expected Behavior

The expected behavior is that telemetry is not sent when it is disabled in the settings.

Anything else?

Found this issue as my bi-directional firewall got triggered by Albert attempting to connect to http://<address>/ after updating.

[ManuelSchneid3r]

This is intended behavior. When telemetry is disabled in the settings, Albert ensures that no user data is sent — the payload is entirely empty. What remains is a simple "ping" which serves the purpose to maintain a user count estimate. This minimal information allows to better understand the public reception of the project without compromising privacy or sending sensitive data.