This concludes what may be the longest tweet thread I've ever written. Interested to hear your thoughts!

https://safelibs.org
safelibs.org/apt
hub.docker.com/r/saf...
github.com/safelibs/

If you want to chat in person, I’m at DEF CON Singapore at DEF CONAcademy!

📄 Title: " Thermoresponsive self-blocking electrolytes and separators for intrinsically safe lithium batteries"✍️ Lead authors: Prof. Liquan Chen (Academician, Institute of Physics, Chinese Academy of Sciences), Prof. Guanglei Cui (QIBEBT)
🔗 DOI: doi.org/10.1016/j.gr...

#SafeLIBs #thermoresponsive

For the latter, I created a repo of library functionality validation scripts that people can report bugs against (github.com/safelibs/...), which I'll slop testcases from and then have a Test workflow step fix the port to pass the testcases. I think this will be a good balance.

I solved this with a hierarchical workflow for the high-level process, with complex individual steps dynamically creating library-specific workflows. The main high-level steps I'll describe here are Recon, Setup, and Port, but the full workflow is here: github.com/safelibs/...

If you want to ignore the "how" in the rest of the thread and get to "what", you can find translated libraries (two million lines of rust!), easily apt-get installable, at https://safelibs.org! Enjoy!

For the interested readers, we'll dig in below!