Working Thread

[dstroy0]

post what you're working on, little blurbs, or ideas, this is for thoughtstreams.

[dstroy0]

refactoring codebase, security hardening (owner refactor) remove globals now that core is integrated and switch to known security patterns for owners, mutable global ptrs no longer necessary to support speedy implementation. Then remediate sonarqube code smells and codeql gripes. Then look at more niche codecs, write some pure codecs from old manuals, stuff that you wanted a while ago but never got around to capturing and putting down on paper. Strip an esp to bare metal and do very legal things with the radio as a plugin for the server. Update the pentesting suite to cover more cases, get creative, try to break the server.

[dstroy0]

Extending test coverage. Provably dead lines are getting gcovr excluded with rationale inline. Be conservative with the exclusions, even if the test is pointless, it's to teach. That means guarded dead branches or unreachable guards are the main exclusion targets.

[dstroy0]

I need to chart how the docs are scraped and built, keep refining and implementing automation in the gaps to increase maintainability and catch outliers to refine the end documentation product. The color palette is really close but still a little off, there are a ton of alignment issues. Conceptually squirty's house is right, bubbles, rocks, sponge, but it needs refinement, so does his behavior. Need to add a switch to sandboxed docs for teachers to turn it off completely. I made a bunch of silly themes so I should let users preview them on live docs. Maybe? I don't know. There are Grand Canyon sized gaps in the docs and stale sections. I need to do a full audit of the docs instead of being creative with grep and viewing the diff.

[dstroy0]

I need to write a spi driver for a w5500 to support non rmii ESP32 like the S3.

[dstroy0]

make Industrial_ESPIDF/ and write the cmake for them

[dstroy0]

refactoring enums to enum class lib wide to eliminate any chance of them leaking across translation units, part of reasonable side-channel hardening on the esp32, enforcing single assignment per line code styling, ternaries are fine for me but a no no for production. I should get out of the habit of using them for rapid prototyping.

[dstroy0]

updating CI so it only runs affected env files with full run as safe fallback

[dstroy0]

Implementing more crypto. Implementing more codecs for more iop. Someone has an oscilloscope that needs WiFi telemetry cap and we need to support TE and ATE anyways.