Today's featured function: makeitworksomehowwithoutregardforkeycontinuity. Does what it says.

TIL that Fn-4 (not Fn-F4) will suspend my thinkpad.

Hot or not take: RSA should be treated like lead solder. If you want to use it, you have to fill out a form explaining why you can't use a safer alternative.

Tried wearing "quick" "dry" "technical" "fabric" "travel" shorts on a hot day. Now my phone screen is steamed up like it came from the sauna. Better living through technology!

Got my first Block. Which raises the question, what is honk supposed to do? Extra not talk to you?

Also, Pleroma peoples, I think I was supposed to not receive this? Spec says Block is client to server, but explicitly not federated to the object? Or is current practice other than specified?

The disclosure timeline in this post is a thing of beauty. "Quarkslab replies that it is not possible to coordinate disclosure if one of the involved parties -the reporter- has no information about whether the bugs are confirmed and if and when the vendor plans to issue fixes, and that it cannot agree to sign an NDA that would prevent reporting to customers and the general public and provide transparency about how the disclosure process was handled." The rest of the post is great too.

https://blog.quarkslab.com/reverse-engineering-broadcom-wireless-chipsets.html

UX fail: Door has security code 1234. Some joker pushes 9, walks away. I enter 1234, lock sees 9123, beeps angrily. Then *remembers* the 4. I enter 1234, lock sees 4123, more beeping. Repeat, repeat.

"The emperor is naked, but I rolled some dice and at least these values aren't zero." Points for style at least... Sounds like a comment you'd find under the games/ directory.

https://docs.freebsd.org/cgi/getmsg.cgi?fetch=553776+0+current/svn-src-head

Many thanks to @kaniini who figured out what I was doing wrong while trying to communicate with pleroma.

Something else that's been really frustrating the past few days: Hyper Light Drifter. But not in a bad way.

A federation complaint that's actually a browser complaint: I crashed chrome by running it out of file descriptors trying to see what a honk looked like on another site.

Version Twosday is here. honk v0.2.0 reclassifies even more bugs as features. Most of the things that were kinda iffy (but not deliberately so) in 0.1 are now better. Even got to test database schema upgrades.

This also concludes the first round of our scheduled live fire test honking. We will return to regular boring noise making soon.

https://humungus.tedunangst.com/r/honk/d

Adding retries to message delivery has had exactly the expected effect: further rounds of failure.

Now possible to attach text files to honks. Useful for diffs, etc., and though email is perhaps better suited, I've already received two patches via links to paste sites, so this should reduce friction.

As ever, somewhat mysterious what happens with other software.

Attachment: smalltest.txt

In other news, it seems the quick workaround for pleroma didn't take... Perhaps I misunderstood what's needed.

This looks like the commit (https://git.pleroma.social/pleroma/pleroma/commit/cf9ba8fe1b5a701488889c4bfdde46e7f00b9ebc) but adding summary to honks didn't result in fewer 500s.

One mystery solved. Mastodon really does just ignore crappy deletions. https://github.com/tootsuite/mastodon/pull/10326/commits/f738c690234daefa1fd6bd9ed8f11508ffff3496 I would say if you're sending so much crap you DOS yourself (https://github.com/tootsuite/mastodon/issues/9377) the solution would be to send less crap...

The entire idea seems suspect. The servers you know about are not the same as the servers that know about you. No reason to even believe there's significant overlap. Instead of notifying the correct people, it's just useless noise.

Weird... glitch-soc sets the "actor" of an update activity to the id of the note being updated. honk disapproves. self-updating statuses is how the machines take control.

Another problem with deletion in the federation: messages arrive out of order. More than once I've received the delete first, followed by the create. Result: not deleted.

Extortion spam hilarity: the guy who keeps hacking my webcam and demanding hush money has moved his message from text to an attached jpeg to avoid filters, but didn't alter the instructions about copying and pasting his bitcoin address, which is now impossible.

Oh, this is hilarious. The was a 128 pixel crop of a screenshot. Heavy M somehow found the original dimensions in the meta data, and most helpfully uncropped it into an enormous desktop sized png.

now supports custom emus.

Interesting. If I search for "remove duplicates array" the first 20 or so results are all about javascript. (Use filter, but no discussion of runtime or efficiency.) If I add unsorted to the query, the results switch to java and the answer changes to sort it first, which defeats the purpose.

Exciting new federation failure mode: IPv6. Even IPv6 "only" servers may have 6to4 gateways. But federation requires two way comms for key exchange, follow/accept dance, etc. and IPv4 server can't reply to messages received from IPv6 only.