Guerrilla Software Liberation
If you have access to software or hardware documentation that is proprietary and is otherwise undocumented, it is your duty as a good librepunk to leak it.
This includes API documentation, Verilog, schematics, and source code.
Make torrents, put it on IPFS, put it on every git instance imaginable.
It's important to leak source code separately or clearly label such a thing so folks can use the "Chinese Wall" method of reverse engineering so the free implementation is completely legal to share. If it isn't, it will not replace the proprietary alternative effectively.
More information here: https://en.wikipedia.org/wiki/Clean-room_reverse_engineering#Reverse_engineering
Also please note that this post was inspired by the "Guerilla Open Access Manifesto" by the late, great Aaron Swartz.
If you liked what I just said, you'll probably love his piece.
It's available here as a webpage: https://archive.org/stream/GuerillaOpenAccessManifesto/Goamjuly2008_djvu.txt
And here in plaintext using the US archive.org CDN: https://ia800605.us.archive.org/15/items/GuerillaOpenAccessManifesto/Goamjuly2008_djvu.txt
Shutout to deletescape/exconfidential for being an avid Guerrilla Software Liberator. They've done so much for the libre software community by leaking hardware documentation and source for previously undocumented (or poorly documented) hardware.
@polarisfm librepunk is a great fuckin name!
@Justhinkin Thanks! As far as I know the term was coined by @/firstname.lastname@example.org.
A friendly mastodon instance primarily for shitposting, gays, and the glory of the free and open source software movement.