Document your APIs.

And don't lock them up.


If you try to lock them up and heavily obfuscate them I will pull another 36 hour day and document them all.

My first real public project is coming.

I deserve a purple heart for figuring out that API.

More info soon.

Show thread

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:

Show thread

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:

And here in plaintext using the US CDN:

Show thread

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. :trans_heart:

Show thread

@Justhinkin Thanks! As far as I know the term was coined by @/ :blobcatpirate1fluid:

@polarisfm @thufie Tillie runs, which doesn't process DMCAs, and if you let them know about it, they'll gladly signal boost any release

Sign in to participate in the conversation
☠️ librepunk ☠️

A friendly mastodon instance primarily for shitposting, gays, and the glory of the free and open source software movement.