Litchralee

@molly0xfff@hachyderm.io This is precisely the math + cryptocurrency joke I needed to start my Wednesday morning!

@clauwn @dec_hl The very first commit from upstream has this: https://github.com/stphnrdmr/ZephCore/commit/8d1823d0b65e61f448c38feb06ad1650cf7c655a#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5R8

Copy the meshcore companion source and hit it with a hammer named Claude until the FW works on the node

@dec_hl Welp, I guess I spoke too soon. ZephCore inherits the cobbled-together protocol implementation from the mainline #MeshCore repo, while also indicating that Claude was used to port it from Arduino to Zephyr. While I could try to stomach this use of AI, the fact remains that just changing out the driver layer to use an RTOS does not reduce complexity or make anything cleaner, more modular, or easier to hack on. Quite the opposite, I would argue.

@rbmath @kwf I vaguely recall once seeing a public chess board that was mounted atop a spinner, so that it could always be oriented properly for the players.

@Linux_in_a_Bit@infosec.exchange Oh cool! I was actually looking for more mesh implementations in C++, to draw inspiration for a separate project.

@nullagent@partyon.xyz @dataparty@partyon.xyz @rfparty@partyon.xyz One thing I'm curious about is whether 2.4 GHz LoRA can use a much larger payload size, in order to encapsulate multiple small LoRA payloads over point-to-point links. I can see this making a lot of sense, so that a train of messages can be sent in one go, over a ptp link that is much less likely to have collisions on the RF link.