Google posted, today, about a proposal that corporations should collectively try to stigmatize any open-source software for which the maintainers haven't chosen to publish under their legal names.
Fuck that. Personally we think everyone has the moral right to anonymity. If we choose, someday, to publish software via an anonymous anarchist collective, Google won't stop us.
That really is what it's about. Google wants to put open-source software - which in many cases is written by free, by volunteers, as a service to all of humanity - within the system of state power.
*for free. ah well
Today it's become very corporate, but if you go back to the foundations of the free software movement, it was very much about *reclaiming* technology so it can be a tool of the people.
IBM did not want Linux to run on the architecture it designed. Apple didn't want it to run on theirs. Linux was a *hostile* action to corporate power, from the very start, and fundamentally a very powerful one: Let's just build it ourselves.
We live in the world that was reshaped by the FOSS movement. We can't afford to take it for granted, or it'll be merely a historical aberration and not a long-term thing.
A slight correction: Several people have weighed in to point out that we probably have a distorted memory of how hostile IBM and Apple were to Linux. We think the essential point stands that Linux was written out of idealism and with political goals.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
So first off, let us talk about why we're doing this. We've been using Unix command lines for... a bit over 25 years at this point, we think. In all that time we've developed some opinions.
We don't expect this to change the world. We expect it to be a moderately useful tool. We're well-known enough at this point that it's quite possible people besides ourselves will use it, and if so, we'll be happy. We'll also be happy if we're the only ones who do.
Hey, debugging question. We're writing a Rust program that uses raw terminal input (ie. disables line-buffering), and we're seeing behavior that we think is attributable to the Rust std environment resetting the terminal modes on exit. Is that... a thing?
We would like to find where it's documented, if so, or failing that the source for it.
We could get our code working without worrying about that, but we really want to make sure we're attributing the behavior to the correct component.
We're live-tweeting PEPR20! After the break, this will be the thread head for the fourth block of talks ("session"), which will be the last one for the first day. #pepr20
"Product Privacy Journey: Towards a Product Centric Privacy Engineering Framework", by Igor Trindale Oliveira, is now starting.
Why a product-centric approach? Other possible focuses would be compliance, design, engineering, users... #pepr20
Okay! This will be the thread head for the third session of #pepr20, which will re-convene after the birds-of-a-feather breakout sessions, in about ten minutes.
We have a secret motive for tweeting this, it helps us pay attention. Our brain doesn't cling to things unless we're using *all* of our brain.
Okay, the theme of this next block of talks ("session") is design. So now we're on slack channel 3. #pepr20
Just to keep our tweets organized, this will be the thread topper for our live-tweet of session 2 of #pepr20, when the break is over.
Okay! We're back from break. The talk title went by very quickly, ... now there's a pause, hopefully the speaker will introduce themselves again. #pepr20
According to the schedule, this one should be "Building and Deploying a Privacy Preserving Data Analysis Platform", by Frederick Jansen. #pepr20
Okay! We will be live-tweeting #PEPR20, the USENIX conference on Privacy Engineering Practice and Respect. Feel free to mute that hashtag if you don't want to drown in tweets.