← Feed

Posts

• Post #1166304

  Since we started using `cargo vet` in #ArielOS, I'm happy to see that some of the crates that we previously on our list of "yes we should review them but don't have the resources now" are vanishing from there because other parties we trust have actually reviewed them. The ecosystem is growing! ❤️ #RustLang #supplychain

• Post #1166303

  We're gathering momentum for slipmux, a transport of #CoAP over serial ports. That specification allows #embedded developers on simple boards that just have a UART to use the same tools with it as for talking to devices across the Internet. This includes security: I guess I just sent the first encrypted request over slipmux ever, and its security setup was unmodified from #ArielOS's CoAP example. Implementation is available in #RiotOS (#C), and WIP for Ariel (#RustLang) and #aioc...

• Post #1134308

  RE: https://hachyderm.io/@epage/116222972742950673 I've known that #RustLang's Cargo has been taught to not update dependencies that it can't use (because they require a newer Rust version), but just learned that it can be told to respect the own crate's MSRV for that: CARGO_RESOLVER_INCOMPATIBLE_RUST_VERSIONS=fallback cargo update allows me to utilize this even though my MSRV is so old that Cargo didn't have that feature back then. Thanks to @epage fo...

• Post #890441

  With the speed around #JpegXL picking up (now in #Firefox and #Chrome nightlies), I'm wondering what good use of an #HTML srcset would be there. As JXL's progressive compression is good, we don't need different files in the srcset (so there's no need to load the first few KiB again when zooming in), but how can or should the HTML somehow tell the browser that for (say) up to 800px width it can request the Range: bytes=0-12345, and the next usable zoom level of 16...

• Post #890440

  Funny how people, in light of the LiteLLM compromise, jump to the conclusion that the solution is to make your supply chain even more intransparent by vendoring in dependencies through an LLM's processing, rather than just using pinned and vetted dependencies by default over tools' defaults "yolo there has been an update and it claims to be semver compatible" attitude.

• Post #890439

  Preparing a demo for the @ariel booth at #CLT. If things goes to plan, you can control different #embedded systems running the same application from your browser. #CLT2026 #IoT #CoAP

• Post #634399

  As @Codeberg's CI is seeing regressions around #IPv6, I'm exploring @codefloe, which uses a Woodpecker fork called Crow. Among many other nice things, it features a pipeline dependency graph. So far, this looks quite promising.

• Post #568667

  Trying to understand recent #RustLang activities (https://github.com/rust-lang/compiler-team/issues/922), why do types with uninhabited fields (or enum variants that are uninhabited) take up space at all? Example at https://play.rust-lang.org/?version=nightly&mode=debug&edition=2024&code=use+core%3A%3Amem%3A%3A*%3B%0Ause+core%3A%3Aany%3A%3A*%3B%0A%0A%23%5Ballow%28dead_code%29%5D%0Astruct+DataPlusInfallible+%7B%0A++++a%3A+u8%2C%0A++++b%3A+u64%2C%0A++++c%3A+core%3A%3Aconve...

• Post #568663

  If you depend on a third party linter to use a system securely, maybe you shouldn't use that system in the first place. (What's the term for a subtoot when it's for a commit/PR?)

• Post #215840

  I appreciate how #DeutscheBahn makes working on a train easy for #embedded development.