Well done, this should be law and apps like Uber should have to turn off their tip screens to operate here.

Fairly sure this is a regression in the current release, i just ran into the same thing after upgrading to 1.34 and went back to 1.31.1

Your message likely didnt get to any recipients. When you send a message it will send, wait and listen for other nodes forwarding your message, then retry if it didnt hear, up to a limit. It got to that limit without hearing any other nodes. It is possible however your message did get received and you just didnt get the reply.

I dont entirely know but I can take a stab - I think it's likely that either that node's owner pulled your node's public key and started using it (probably not), or, more likely, these tiny devices dont have a lot of entropy to work with when generating keys leading to less randomness and more collisions than should be likely for the algorithm and key size. Basically, you should probably regen your keys to make sure, as that node may have the same keys by accident. Make sure to tell people you know on the network to delete you as key changes are not handled well and will probably lead to broken (or at least broken looking) dms until your node is deleted and rediscovered.

That would actually be a fairly cool ui feature if it could be calculated...

They have their location broadcast accuracy turned down so as not to reveal their exact location

ah, nuts. Ive always worried about leaving mine with li-ion batteries in the car given how hot cars get

pretty 😃

anyone know of a qmk mouse board that's smaller than ploopy?

I can see both under (gaps between lines) and over (at the edges of the first layer) extrusion in that photo, so i think it's likely one of orca's calibration settings. Does it still happen if you use completely stock settings in bambu slicer? If so, I'd go back to defaults in orca then start tweaking again from there.