chexum

@geerlingguy hmm, one of the reasons wifi chipset vendors (for example to provide #OpenWrt support) more and more grown to refuse not just source code but also hardware/programming specifications because of a blind reference to the #FCC not allowing it. It’s understood that with documentation *anyone* can then modify it to use frequencies or modulations not permitted by the #FCC This is now a completely useless argument, if the FCC doesn’t approve routers anyway, so I’ll say, let them release the full specs! It would actually benefit the router ecosystem to bring up everyone to at least the security of OpenWrt…

@LovesTha @mhoye the hex based conversion covers what I need… 30 mph is about 0x30 km. The other direction is not as trivial but gives a good approximation if you can recall all seven bit numbers in both bases — 64 km “is” 0x40, so 60ish kms are 40 miles. It gets funky with things like 55 miles as 55 m is not 85 km but 5 needs to be converted separately…

@saddestrobots@jorts.horse @scottmichaud@mastodon.gamedev.place my solutions to search stuff are: find | grep bla find | xargs grep bla It doesn’t work of BSD and OS X. I try it at least five times a day as I use a Mac everyday. Sure I accept it was made to work this way, but really, would it hurt to allow me to type two characters less?

@szbalint@mastodon.social ISS Remote Control!