just a quick note about state of affairs.
… family stuff … day work stuff … didn’t have much time the last days.
did optimize the udp-holepunching library a bit for my purposes, released the new version, stripped down autoprox to only offer a websocket relay (well … and some info routes … but no longer wallet management, data query etc …) and made it use the udp library as first iteration.
next step will be to change the frontend to use autoprox as companion app for own ip/port discovery via public stun servers and to see if the current implementation for frontend-websocket-udp-websocket-frontend communication works as expected (it never does on first attempt) and what changes are needed.
Once those 2 (/3) components are compatible and working together I’ll use pyinstaller to make the first version of windows/linux/macOS companion apps + upload them to the network and link them in the frontend app + test it as App delivered via Autonomi.
Since the App itself lives inside Autonomi then + utilizes Chunks to retrieve its companion App this should already be enough to count as “deployed” according to the rules of IF.
From there I’ll add a simple login scheme that allows account login and account switching + stores the peer info in a scratchpad on main-net. (and from there you won’t input your peer info as ip:port but as a scratchpad address that gets updated by your peers when they are online; I’ll probably add a timestamp too and if it was not updated within the last 15 minutes there is no point in trying to connect because the app updates the peer info in shorter intervals…)
we’re well on track 
ps:
maybe to be a bit more specific about the platforms I’ll build for:
macOS Desktop (apple silicon - so the m1-m4 series - no intel based apple hardware)Linux 64bit (x86 → Indel/AMD and arm 64bit) [so that happens to be 2 binaries …]Windows 64bit
Edit: with the move to WebRTC friends doesn't need a companion app anymore and all platforms are supported out of the box without me building for anything specifically
…later on I’ll utilize GitHub actions or so to automatically create those releases to not having to do those 4 builds by hand on every new release … any maybe publish to autonomi directly from another pipeline … we’ll see if I’ll really go that far … but setting a private key as secret and using that from a pipeline where it has access to a few cents doesn’t look too bad to me …