Liquid seems like a better approach from an engineering standpoint because it is non compressible. But then I imagine dealing with liquid is more of a pain than air.
Github measures/reports the SLA of the individual services.
The external page linked above goes the other extreme and considers it a bad status whenever any individual service is degraded.
In reality the majority of people only use 3 or 4 of the core services the majority of the time but since there's no "core services" SLA/uptime the usability of github for the majority of people is slightly obfuscated.
Part of it is that it considers downtime in any of the services GitHub provides as GitHub being down. So if GitHub had 100 different services, and only one of them was down at any given time (but at least one was always down), then it would show 0% uptime.
On a task by task basis the code Claude generates is pretty good these days.
The biggest issue I see is that it wants to rearchitect the code constantly and I have no faith in my tests anymore because Claude will just "fix" them
Assuming you mean mesh in general:
Meshtastic like projects
- emergency communication
- low power data transfer for sensors
- low data rate data transfer for mobile groups. Air softers use it to transmit information to each other while playing.
HaLow:
- "high" data rate over shorter range, though much higher range than 2.4 wifi
- data sharing between mobile groups like above, but high enough bandwidth for low quality video
It's a fundamentally really hard problem that looks easy on the surface. There is no solution that works well beyond the small scale. Many people have tried. It's the same kind of thing that draws people to try to write IPv8.
reply