Notices by Lars Wirzenius (liw@toot.liw.fi)

@cwebber It's like Android is designed and developed by a company that can throw thousands of CPUs at building the operating system.

Gold toilets are a shit display of wealth.

@cwebber @cstanhope @dthompson

Tired: Someone is wrong on the Internet.

Wired: Many people are wrong on the Internet.

Mired: Everyone is wrong on the Internet.

@cwebber You definitely make me think I should read up on ocap.

Many people seem to think imperfections in communication tools (e.g., email mailing lists, web forums) are the reason communication is difficult and why consensus isn't reached.

The tools may (and probably do) have an impact, but make no mistake: communication is always difficult. See also Wiio's Laws (https://en.wikipedia.org/wiki/Wiio%27s_laws).

In order to have a constructive discussion, humans will need to put in a lot of effort into it. It's not about tools.

Just in case it's useful to more people, I'm promoting this so it's not embedded in a thread: a description of how #Debian handles #PGP keys and why it's not vulnerable to the current SKS keyserver signature flooding.

https://blog.liw.fi/posts/2019/07/02/debian_and_the_sks_signature_flooding_attack/

Error messages and logs are part of software's UI and API.

At work, we're thinking about improving CI and just opened up a call for feedback on the thoughts. Sharing it here too, in case anyone wants to chime in.

https://lists.wikimedia.org/pipermail/wikitech-l/2019-June/092227.html

My next goal is to build, test, release, and deploy every time the developer stops typing for more than 300 milliseconds. I won't even wait for them to save the buffer, I'll just take whatever they have in the buffer and pretend it's been saved and committed and pushed.

Having to manually save files and commit changes is such an unnecessary overhead, which slows down development and progress for no good reason at all.

This toot may be a joke.