Reading the system name, as well as seeing some of the options, can be difficult when this pane does not have focus and the map is displaying behind the pane. Please consider adding an option that all panes can be set fully opaque regardless of having focus/mouseover or not.

EVE's builtin routing will support "connections" which we can leverage by treating each wormhole chain as a totally connected star graph. But this is shortsighted design and restricts our growth

• Alternate routes, warp speed aware routing, and alternate prioritization routing all require us to implement our own algorithm
• A solution must support generating routes without affecting rendering thread performance (browser worker)

• F216

I don't play in null so I have no idea how to test this. Think it makes most sense for those with roles to setup this so that we can auto replicate the correct values to members.

Asking individuals to configure this seems fault prone and tedious. Adding reconciliation is going to be a pain too when we eventually add those enterprise features.

This is new-player reach and thus low priority. But v0.3.0 has an integrated encounters database and pretty okay signature parsing. Perhaps links or an iframe of eve survival could help make the lives of forgetful folks such as myself better when diving into the occasional C3.

Imagine FC drags a system into fleet chat write /wp SYSTEM_LINK and everybody's destination is automatically set with the exact same route

The FC and fleet members sees blips on their map of how many people made it to which part of the map, tackle and scout can pace themselves relative to friendlies, less talking more looking

This is the precursor of corp and alliance sharing. The push notification back end is ready and seems to work well with Cloudflare but we have no idea how much load the user base will generate.

So to avoid being overwhelmed and the project oversteps its seed budget, lets scope the broadcast domains to fleets. This will suck for users but the project for now is just a teaser for what could become

The biggest pain for me personally has always been figuring out which signature is the return hole. When your whole session is primarily probing marking the return hole could be problematic.

Never bothered confirming the viability of this, but the probe scanner accurately displays distance to each signature at 100% signal strength. Just how inaccurate can things be at 0%? Even if it sucks, if everything else is over 10AU away, it's pretty clear which is the wormhole that is 5K's off your ship.