Egonex

4 ms·

1.
by Egonex 6mo ago
People think that with better D2D technology, emergency and telemetry messages will still be short and to the point. These messages will not be like streaming videos. When companies work together on things, like spectrum and constellations
2.
by Egonex 6mo ago
Totally get it. We work on compact binary alerts for constrained links. We have the same obsession with bytes.
3.
by Egonex 6mo ago
This is a very interesting project. Protocol choice on constrained hardware like this is always underestimated, most people default to JSON over HTTP, but on devices with limited MTU or battery constraints the overhead adds up really fast.
4.
by Egonex 7mo ago
The fork itself is not the problem, but presenting it as your own project. Put the upstream link high in the README, say clearly what you actually changed and don't bury attributions just at the bottom.
5.
by Egonex 7mo ago
Nice work, well done. I'm also building a .NET open source project (emergency communications protocol and related systems). I'm curious about your experience contributing to dotnet/runtime. Was the PR process straightforward
6.
by Egonex 7mo ago
This is what we do. We use AI for drafting but we never merge without doing a manual review of dependencies. Every package version is pinned explicitly, and our CI always runs a dependency scan before deploy. The AI is fast at scaffolding,
7.
by Egonex 7mo ago
I will try this in Cursor. The C# tooling in VS Code has improved a lot. I'm curious to see how ReSharper adds to it. Thankyou