msp-osd VS flashdown

This week, as most weeks, I split my time outside of the day job and my other hobbies and obligations between Discord collaboration, Ghidra, and VSCode:

https://github.com/bri3d/VW_Flash - Flashing tools for select control modules in VW MQB and now PQ35 platform cars. This week I'm working on old stuff: a simpler exploit chain for older Simos ECUs, as well as tweaks to expand support to older DSG control units used in PQ35 platform vehicles.

https://github.com/fpv-wtf/msp-osd - I pushed a rearchitect of this on-screen-display overlay system for DJI FPV Goggles last week that seems to have sorted out a lot of issues - I switched from just passing through the OSD drawing messages from the Flight Controller to a system where the video transmitter maintains the OSD character buffer and sends a compressed representation of the screen state. This makes the system much more robust to packet loss in situations where the Flight Controller sends delta updates rather than frame-at-a-time.

I only really started publishing Open Source projects a year or two ago, and while they're pretty much my worst code by any objective measure, I've met some great people and really enjoy working on these. It's fun making things that achieve a goal without so much pressure of deadlines, stakeholders, and competing priorities.

The root itself only gives you full file system access. But with it you get to modify them. The root is also perfectly safe and you won't be able to tell them appart from unrooted ones. For example stuff like this -> https://github.com/bri3d/msp-osd gives you basically 'canvas' mode on the DJI Goggles (though it's still in it's early development phase so still has some kinks to work out).

Probably not from DJI. However, the guys that rooted the goggles have MSP displayport going. It's not flight worthy just yet, using it takes out the goggle UI so you can't change channels/do anything. However, it's looking pretty promising.

I think it's useful as a counter to Postel's law.

Postel's law (or robustness principle) states that you should be liberal in what you accept, conservative in what you output. Hyrum's law shows the danger in being liberal in what you accept.

(Shameless plug: I've just made public an open source CLI flashcard app where the example deck includes a set of Hacker Laws including the aforementioned ones, you can try it here: https://github.com/SteveRidout/flashdown)

I'm working on an open source terminal based flashcard app called Flashdown which uses a simple plain file format both for storing both the card data and your learning progress.

I just made it public: https://github.com/SteveRidout/flashdown

I'm probably too late to this thread for many people to see this, but if you do and feel like trying it out, please let me know how you get on! :-)