I want to inspire a renewed tradition of deliberate, planned software engineering, where quality and reliability are paramount, and flashy eye candy is an afterthought.

Show thread

Sorry for the downtime, all. Namebargain (my domain registrar) transferred all their domains to Register.com (namebargain’s parent company). I knew that was happening, but I missed the minor detail that THEY WOULD NUKE THE DNS SERVER RECORDS.

Anyhow, back now.

We need to defeat this bizzare cognative dissonance people face when they have to re-evaluate the place email holds in their mind. It's not some useless relic of the last generation to cast off in the course of chasing the shiny new.


- Federated
- Decentralized
- Built with open standards
- Fault tolerant
- Enjoys a wide variety of open-source clients & servers
- Has widely available implementations for almost every programming language
- Already being used for software development at scales greater than GitHub-style development has ever dreamed of

"Email? Yuck"

Screw that noise. Set aside your preconceptions and look at email for what it is. The things that make you "yuck" about email are more related to the bastardization of email *software* by corporate interests like Google and Microsoft, and have next to nothing to do with email itself.

Not everyone owns a cell phone.

Not everyone owns a smart phone.

Not everyone has internet at home.

Obnoxious, proprietary vendors who want you to read an EULA for each firmware update for the hardware YOU ALREADY PURCHASED - including presumably for important security updates can not only fuck the right off, but should be fined,.

#NoScript in 2020: you know, I would love to read this Bloomberg article but I don't know which of these 14 untrusted domains has the JavaScript that makes the page load.

The second one is "Being a #GNOME maintainer", and it's a bit of a primer on how I deal with maintaining a bunch of free and open source software projects, both in GNOME and around it: youtube.com/watch?v=IsofCLwxTo

Show thread

Both my #guadec 2020 talks have now been published on the YouTube channel. The first one is "Archaeology of Accessibility", in which I talk about the work I've been doing on #gtk in order to redesign the accessibility API: youtube.com/watch?v=eNh0Xg8abj

Our IT sends me a link to an intranet service. My browser complains, because TLS 1.0

I ask IT to deploy proper certificates.

IT sends me screenshots how to enable TLS1.0 in IE.

I'm crying.

Imagine if we lived in a world where reliable, cost-effective software was the norm, and failures were as rare as they are in other engineering domains. Instead we have a world where everything is fucking half-assed bargain bin shit piled upon 30 layers of abstractions, huge hulking Goliaths made entirely from feces, shoving everything else out of the way as it stumbles painfully slowly towards the window to paint a cat gif on your screen, then failing halfway through and burning your house down instead.



Show thread

Nobody gives a fuck about stability, or testing, or security, or bloat, or simplicity, or even producing software which works in the first place. They just want to spend the minimum effort required to get paid.

I fucking hate this industry.

Honestly if I could boil all design advice down to a single tip, "make it difficult to do the wrong thing" would be it

Show thread

Ooh, look what just arrived.

(It’s the PinePhone UB Ports edition.)

Looking forward to sharing my experiences and thoughts once I’ve had more of a play with it.

>Microsoft Defender SmartScreen is hurting independent developers

Water is wet. It's working as designed. Get off the platform, idiot.

Just a reminder to people @gamingonlinux doesn't need to cover what *you* want and skip over what *you* don't like.

We serve the Linux gaming community, not single interests. We try to cover a bit of everything. Deal with it.

android is truly a preview of the cursed world that is yet to come in consumer computing
Show thread

You know, I empathise with GitLab here. git.sr.ht had a memory leak once. My solution was pretty interesting: I wrote a shell script on a cronjob set to every 5 minutes, which checked the heap size of the git.sr.ht backend and, if it was within a certain percentage of system memory, it sent a SIGTERM along and

Wait, no, none of that is what happened. What happened is I fixed the memory leak.

Show thread



"GitLab has memory leaks."

Their solution is monkey patching their application to check its memory usage after every 16th HTTP request and commit suicide if it's too much. This page is telling sysadmins who install their own GitLab instance how to configure this.

Show more
Mastodon for Tech Folks

This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!