xianc78 @xianc78@gameliberty.club

Today is a special day -- #codeauditday !

How do you celebrate?

On this day, developers around the world, whether or not they are actively employed or would normally do so, take some time out of their day to pick apart some part of their software stack that runs the technology in their lives. The goal is to take, once a year, a little extra time to audit, or test, or verify and validate the technology in our lives. The goal here is so that, as we continue to develop more and more complex technology that we never entirely lose our ability to understand it, at least in part, and that we always have some idea of what the computers in our lives are doing, in some decentralized, organized chaos way.

To participate in #codeauditday, pick something, some software, some code that you are currently running or have recently run, find the source code, read it, and understand it. Consider using a fuzzing tool or running the unit tests. Make sure it builds. Use some legal marijuana and/or meditate to help gain insight if that's your thing. There's lots of things you can do to source code to help make sure that it actually works, is robust, and works for *you*...do that stuff. Whatever you choose to do, whatever you choose to audit, don't be afraid to ask questions, to share what you're doing, and to generally have fun. Software doesn't have to always be painful, boring and life draining to debug.

For a past code audit day I suggested (as root)
for debian/devuan/ubuntu/etc users something like

# dpkg -S `cd /; ~/dirrand4 2>/dev/null | head -n 1`

which should tell you the debian source package you'll want to poke around (you'll need dirrand4 from https://notabug.org/themusicgod1/tools for this)

And sure, most people will chose software, either randomly through a tool like dirrand4 or just on their own, that is common and there'll be some duplication of effort. This is normal and healthy -- software that is common should be that much more closer scrutinized

another thing that would be handy to write for this day would be a tool for npm (and similar tools/platforms, like rust) that grabs a npm(or equivalent) project, and grabs its dependencies, and chooses a random number between 1 and N (where N is the number of dependencies+1). if that number turns out to be 1, it terminates and outputs the name of that package, otherwise it grabs the dependency (chosen by N) and recurses

http://b4hntuy3fimfh2227vf4f74emnya7p35i5brtqujs6leqvtclfwvjbqd.onion/googleplus/20171010%20-%20Today%20is%20code%20audit%20day!%20%20I_m%20starting_.html

Article by someone who claims to work at Microsoft talking about anti-racism leading to racism:

https://www.cspicenter.com/p/what-diversity-and-inclusion-means

Degrees of Statism