While I like the new client-side media processing feature coming today in WordPress 7.1, I really don’t like that it’s (at least for now) a Chromium only feature. So neither Safari nor Firefox can handle media processing on client-side at the moment. A real bummer for the open web …
Statuses
-
TIL: Finding new devices in LAN required for ping
TIL (actually, it was yesterday): Disallowing the terminal on macOS to find devices on the local network prevents them from connecting to new local devices on the network. However, if you were already connected to them before, these connections work fine.
Response in the terminal for pinging new devices is just a “Now route to host”.
-
Today I learned: Leave WordPress category alone
TIL (again): Leave the default WordPress WordPress category taxonomy alone for your custom post type. The probability is high that you’ll regret it in the future …
Just register your own taxonomy.
-
Replaced Sentry with Bugsink
-
Energy Efficient Ethernet via FritzBox is not good
TIL: Energy Efficient Ethernet (EEE) in the newest firmware (8.2x) of my FritzBox is probably garbage. When set to “automatic” (which is the only setting aside of “off”), the network is super unstable between devices on the LAN/WAN and any other device. In both the LAN and the internet.
Clear suggestion: if you have connectivity issues after the update, disable EEE in your FritzBox’s network settings.
-
Dovecot update is not fun
TIL (at 3 am): Upgrading Dovecot is not fun when the behavior changes a lot. Took several hours to get it running identical to before. But at least I could remove some old configuration parts.
-
Default value in register_post_meta
TIL: Defining a default value within
register_post_metadrives you crazy if you no more aware of that you did it. It still persists, even if it is not in the database or the object cache.Found out around an hour later … 🥲
-
Why something new?
Every so often, I read and hear that Apple is no more innovative because the devices look always the same (not the only reason, but let’s focus on this).
I just don’t get why. Why it needs to change? I’m not against new, I’m just happy with my devices. iPhone: it works fine, would even love to get back in time where an iPhone could still stand on the table without help. MacBook: I love the design, why bother with something new, just for the sake of something new? We’ve seen where this ended with Liquid Glass …
(This is no rant, I’m actually curious what thrives the people.)
-
Replaced Numbers with something completely different
I used to use Numbers usually only to track my spendings for my side business to get a quick overview when doing my taxes. All the back and forth with Apple Creator Studio now let me change that.
Now, I’m using InvoiceShelf to track the expenses there. It’s self-hosted and thus I’m in full control of the data. And I can add nice analytics of this data, where it was only a list before.
-
Migrated away from Audible
I used to use Audible, because it was convenient and cheap for single audiobooks. Now, I migrated away from it by using Libation – a great project to download Audible content – Jellyfin for managing the audiobooks, and BookPlayer on iOS, the latter came through a suggestion from @simon@dewp.space.
Absolutely recommended. Especially the app is so much faster than Audible, which takes ages to even display anything. And way less battery-consuming.