Fly safe, capsuleers o7
I’ve been building Telescope, a desktop app that reads your EVE chat logs, runs the lines through rules you control, and turns the matches into alerts on interactive maps of New Eden. Version 1.0 is out. I’d love for you to try it and tell me what breaks.
What it does
Telescope is a desktop application that watches your EVE Online chat logs, evaluates them against configurable pattern rules and shows the resulting alerts on interactive maps of New Eden. Characters linked through EVE SSO are followed through ESI so the maps can show where they are and warn about nearby threats. It is similar to other intel gathering tools, but with some key differences.
- Designed to be multiplatform (Windows, macOS and Linux).
- Designed to be as easy to use as possible.
- Designed with privacy in mind. Your data resides in your computer.
Privacy and ESI
Everything lives on your machine. Linked characters, corporations, alliances and tokens are stored in a local database encrypted. There is no Telescope server. The login runs through CCP’s official SSO page.
Telescope requests these ESI scopes:
publicData ()
esi-location.read_location.v1 (*)
esi-location.read_online.v1
esi-clones.read_clones.v1
esi-characters.read_contacts.v1
esi-alliances.read_contacts.v1
esi-corporations.read_standings.v1
esi-ui.write_waypoint.v1
Version 1.0 uses publicData and esi-location.read_location.v1 only: they show where your linked characters are and how close an alert is to them. The other scopes are requested now for [planned features, e.g. standings-aware alerts and waypoints], so adding them later won’t ask you to re-authorize. Nothing is sent anywhere except to ESI. You can revoke access at any time from your account’s authorized applications page.
Under the hood
Written in Rust with egui/eframe. One codebase for Windows, macOS and Linux.
Intel runs on its own threads (log watching, rule evaluation, alerts), so an alarm isn’t delayed by a hidden or stalled window. The rules are a node graph stored in the local database, with the rules.toml import/export for versioning and sharing. Reference data comes from the CCP SDE, built into a local database and kept up to date automatically. Location tracking is a background ESI poll per linked character. The workspace is split into crates (rule engine, settings UI components, native tools). ARCHITECTURE.md in the repo maps the modules, threads and main flows.
CI builds, lints and tests every change on Linux, Windows and macOS.
Download
Windows (MSI) and macOS (dmg): Release 1.0.0 · rafaga/telescope · GitHub
Linux: build from source (cargo run --release, see BUILD.md in the repo) In theory runs on Linux but it is not tested
Source, docs and screenshots: GitHub - rafaga/telescope: Application to gather intel from Eve Online, visualize it and generate alerts from information · GitHub
I’ve tested it by hand on Windows 11 (x86-64 and ARM64) and macOS Tahoe (Apple Silicon).
First-run notes
macOS: the app is self-signed, not notarized. If macOS blocks it, you need to authorize en privacy settings
Windows: the installer isn’t code-signed, so SmartScreen may warn on first launch. More info → Run anyway.
Feedback wanted
Did your intel channels and your own phrasing get detected? What did it miss?
What would make the default rules better for your alliance or region?
Bugs, crashes and rough edges on your platform.
If you build intel tooling yourself, I’d value feedback on the rules format and the ESI usage.
Report problems on GitHub
And there is a Discord server If you want to give your feedback.
Telescope is free and open source. It is a fan project and is not affiliated with or endorsed by CCP Games. EVE Online and the EVE logo are the registered trademarks of CCP hf.
Thanks for reading. o7