XIDER / TARPED
OWNER-AUTHORIZED · WINDOWS + macOS
XIDER is source code for managing devices you own or are explicitly authorized to manage. A Telegram bot checks access, routes a signed MQTT command, and the selected endpoint agent returns its result.
Source version 4.3.0 · a source number is not proof of an installed or published package.
Submission is not proof of completion. The agent must return a result.
THE SYSTEM, IN PARTS
Each component has a named responsibility; interface wording does not change access rights or command behavior.
Telegram interface, role checks, device controls, and release catalog.
Windows and macOS agents that receive an authorized command and report a result.
Reports supervisor state and can recover its agent according to local configuration. It cannot wake an offline or powered-off computer.
Signed agent-update flow and a catalog of GitHub releases. Selected versions require owner confirmation and signature checks.
Six interface voices: X-TECH, X-PERSON, X-PIKMI, X-TARPED, X-CORE, and X-ADAM. Wording only; permissions stay the same.
TRUST IS A DESIGN CONSTRAINT
Designed for the owner’s devices or devices they are explicitly authorized to manage. Not a way around operating-system consent.
The protected owner is defined by configuration. Other accounts can be users, guests, or blocked; user access is scoped by device and action grants.
MQTT uses TLS and HMAC-signed messages. Payload encryption depends on ENCRYPT_PAYLOAD and is not assumed active in every local setup.
An online indicator means a recent heartbeat, not guaranteed availability. IP-based location is approximate, not GPS.
Camera, microphone, screen capture, and other protected capabilities need an authorized command and applicable OS permission. Sending a command alone proves nothing about physical completion.
Source code, release history, and offline test fixtures.
Live Telegram, MQTT, production VPS, or physical Mac/Windows acceptance.
Check the release notes and acceptance checklist for version-specific results.