Show more

Wow, so I didn't mean that I got sick from taking the flu shot. You're supposed to feel a bit tired the day after as your body gears up and makes antibodies.

JFC, get vaccinated, do your part to keep society as a whole healthy.

The closest I've ever come to dying was a few years ago, with a particularly nasty case of the flu.

Woke at 04:30, and couldn't get back to sleep.

There is just not enough coffee for days like this. Especially when it's the second day in a row...

☕ ☕ ☕

My chromebook just updated to Chrome OS 70. (beta channel)

I *hate* it.
Like, die in a fire hate it.

No more individual notifications in the status bar, just a circle with the number of outstanding notifications. So, now I can't tell at a glance *what* is trying to notify me, and thus, can't tell how important it is. And the persistent notifications for things like outside temperature are now completely useless.

69 made me so happy with Linux app support, now this dumpster fire.

When someone submits a feature request or "bug fix", and the first thing they do is list all of their credentials...

You know it's going to be:
a. Impractical
b. A complete violation of all existing protocols
c. Batshit Nuts
d. All of the above

Note that the credentials almost ALWAYS include MS certs.

This week's theme:

"Why didn't you have systems in place to prevent X?"

"Why would anyone *DO* that?"
When dealing with the general public, IMO, the "reasonable person" standard should always be used. If your consent/license form cannot be understood by a reasonable person with average education, it should be considered legally invalid.
The tech industry needs to take a page from the medical community on Informed Consent.

#1, everything you do that affects me needs to be done only with my active consent.

#2, Informed Consent does not mean 18 pages of legaleze that even an attorney would need four days to understand, and would probably still miss one or two loopholes. Informed Consent means I have to actually UNDERSTAND what you are asking me to consent to. It must be in plain language, not legal-speak.

Watching the slack messages go by for a project involving three different teams setting up systems for a fourth team. Where none of the three teams have actually dedicated any time to the project, and none really care much. So it's messages thrown back and forth between their other tasks, usually hours between.

I figure the systems should be built and available some time in 2021. 🤦‍♂️ 🤷‍♂️

dev rant 

The problem I have with coding in Perl, is that there's easily dozens of ways to do the same thing, and some ways are demonstrably better than others. But they're mostly non-obvious, so unless you write a lot of perl code, the way you chose is almost certainly crap.

I know everything is HTTPS-first now. But migrating old apps/sites to be https-compliant is many times not as easy as "install cert from Let's Encrypt".

Helpful hint for the OCD #1248

If you are in the middle of the workday, no matter how boring the conference call is, do not pop off one of the keycaps from your keyb....

You just did it, didn't you?

Yes, it is disgusting, and no, you won't be able to ignore it now. So, you're going to get soap and water?

What? Well, yeah, it's pretty bad.

Yeah, I'm pretty sure that flamethrower will sanitize it.

You sure you want to do t#@$%^(*!

Language rant 

I've been catching up on unit tests for old code for the past few days. I really hate writing them, but watching the code coverage percentage getting closer to 100% triggers my competitive and OCD tendencies, which keeps me doing it.
But my last commit message today was "more unit, much test", which make me think it may be time for a break.

Past me didn't document a thing that should have been documented, so present me spent an hour re-figuring everything out and documenting it.

Past me is a jackass. Don't be like past me. Document your things.

@shatteredgears This should work - http: [ip: {127, 0, 0, 1}, port: 4000]

But it sounds like you're editing prod.exs ? , you might want to generate a config first and edit prod.secret.exs
In my case this is how the config was generated by default.

Finally gave up and set iptables rules.

/sbin/iptables -A INPUT -p tcp -s --dport 4000 -j ACCEPT
/sbin/iptables -A INPUT -p tcp --dport 4000 -j DROP

Not a fan of doing it that way, since it's easy to forget something set elsewhere.

Network app developers: Listening on by default without telling the admin how to easily change it is a FRIKKING BAD IDEA!!!

Pleroma admins:
pleroma is running on *:4000 with apache proxying to it via
Is there a way to configure pleroma to only listen on Or will I need to just iptable that?

@shatteredgears Clarification. The 500 error occurs when I try to "follow from a different account" (I have multiple accounts set up in Subway Tooter). It doesn't happen if I follow from within that account's timeline. So would appear to be something specific with Subway Tooter?

So, in all, I'm finding Pleroma pretty easy to deal with.
The install wasn't horrific, and was probably more involved than most because of running CentOS/Apache rather than Debian/nginx. Part of that ended up with me running certbot in full-out manual mode. Still, I've dealt with FAR worse.
The only oddity I'm dealing with right now is attempting to follow someone from Subway Tooter results in a 500 error from my pleroma server, where doing it via the web UI works fine.

Show more
Mastodon for Tech Folks

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!