For now single container runs all softwares. tradeoff with dockur/windows limits, saves ram and disk. planning multi container later for better isolation.
yeah.. I also agreed with that. so I'll optimize the code continuously and lower the dependency on python. but for now I'll keep it because of some benefits.
Right, I had WinApps pinned to dockur in that comparison and missed the IP-based flexibility part. That's an actual difference, will fix the README.
On Python: fair pushback. Picked it for stdlib coverage (zero runtime deps on 3.11+, one tomli fallback for 3.9/3.10) and iteration speed. Heavy lifting is in the container and FreeRDP so perf hasn't been the bottleneck, but yeah the language choice is a tradeoff.
Reverse file association is interesting, hadn't thought about that direction. The v0.3.0 agent could probably handle it but I'd want to look at the security model first. Marking it TBD. If you open an issue with the use case that'd help me scope it.
The fan body itself follows standard 120/140mm dimensions, but I needed the smaller details for my design, the rubber dampers, anti-vibration corners, cable routing clips. Those don't show up cleanly in the datasheet, so I ended up using a caliper. That's the part the official CAD would have helped most with.
Would have saved me time on a 3D printer I designed a while back. I integrated Noctua fans and ended up measuring mounting dimensions by hand. Having the official CAD models would have made fan integration a lot cleaner.
Codeberg / Forgejo are also out there as less radical alternatives, so the choice space isn't binary. But the discoverability gap is real, and so is the loss of all the surrounding infrastructure people don't always think about. CI runners, release hosting, container registry, security advisories. You can replace each of those individually, but doing it all at once is a significant maintenance burden for projects with limited maintainer time.
Self-hostable legal AI as open source is a useful direction in principle. Hard to tell how mature the actual implementation is though, the repo is pretty fresh and the marketing site is doing a lot of heavy lifting compared to what's in the code right now. Will be more interesting to revisit in a few weeks.