Simplify installation and packaging

[olalie]

Ongoing work to simplify installation and first-time setup.

This includes packaging and other improvements that reduce installation friction.

[forthrin]

Interested

[olalie]

Status update:

Completed:

• Windows installer
• Linux packaging
• Signed and notarized macOS DMG
• Automated cross-platform build and release workflows

Remaining:

• Windows code signing

The issue will remain open until Windows code signing has been resolved.

[forthrin]

Great progress. Homebrew is hopefully not too fara way!

[olalie]

Homebrew support is now available through the official Homebrew Cask repository:

brew install --cask tapmap

Since July, TapMap has also gained Application Information, background operation through the system tray or macOS menu bar, automatic startup, Significant Connections history, MQTT notifications, and native desktop notifications.

Thanks for your interest and patience, @forthrin.

TapMap is eligible for the SignPath Foundation program, and signing currently works with the test certificate. Once the production certificate is available, I plan to submit TapMap to the official Windows Package Manager catalog so it can also be installed with winget install TapMap.

This issue will remain open until Windows code signing is available.

[forthrin]

$ brew install --cask tapmap
Warning: Cask 'tapmap' is unavailable: No Cask with this name exists.

[olalie]

Did you run brew update first? The cask was added today, so your local Homebrew metadata may not have been updated yet.

TapMap is listed here: https://formulae.brew.sh/cask/tapmap

[forthrin]

WFM. Though ran into a walled startup (locate database files) rather than a flying start with previous versions.

[olalie]

I upgraded from TapMap 1.14.0 to 1.14.1 through Homebrew without any problems.

Did TapMap fail to find the existing database files in ~/Library/Application Support/TapMap after the update? They should be preserved and detected automatically.

Please let me know what happened so I can investigate and fix it.

[forthrin]

1. GeoIP data just needed to be installed in the first place, but the wall GUI was overwhelming/confusing. From its appearance it seemed to involve manual downloads, locating files on hard drive, etc. Suggest to largely simplify this. Any "in your face" wall on (first) application startup is a huge barrier to use, and the earlier such things happen, the more users you risk losing.
2. If the program process is already running, no browser tab is opened if you double-click the application. And the process doesn't respond to kill, so you think something is inherently wrong.
3. After opting to download GeoIP, nothing is shown in the map area. Just black. Though when doing kill -9 and double-clicking, then the map appeared. This however shouldn't be necessary.
4. Pressing ⌘ + L to focus browser address field, simultaneously triggers L functionality in the web application.
5. With its self-proclaimed, relentless love for the eighties, and without further comparison, shouldn't the map have parabola trajectories showing how each initially visited site sends requests to other sites?
6. Why aren't Providers and Apps clickable? One intuitively expects them to be.

[olalie]

Thanks again for the feedback.

I have fixed two of the problems in TapMap 1.14.2:

• GeoIP data is now refreshed after the databases are installed or updated. Restarting TapMap should no longer be necessary.
• TapMap shortcuts are now ignored when Ctrl, Cmd, or Alt is held. Cmd+L should therefore only focus the browser address field.

I will look into the other points later.