As one of the few people who use Siri every day I mostly use it to control lights and temperature in my flat.
Every evening I make sure the heating is turned down to 15º (Celsius) and every few days Siri tries to barbecue me in my sleep by misunderstanding my commands.
Every morning I go through the same routine of two completely unnecessary steps when entering what I read the night before:
Even though I’m never reading more than one book at the same time, the GoodReads app forces me to “select” that one book manually. Even though I’m opening the app via the “Update Progress” shortcut, where the app could easily be smart enough to realize that there is only one book for which I can update the progress.
After entering the new progress value, I’m thrown back to the selection screen from before. With the same data from before. To make sure my data was actually saved and not sacrificed to the gods of package loss, I have to manually refresh myself.
It’s has been 20 0 days since we encountered an annoyance within the aura of the Music.app.
There’s this handy feature where you can “Pause” a song by right-clicking the icon in the Dock and then selecting “Pause” from the menu that pops up. Today I realized that this doesn’t work if you have a dialog open in the Music.app, this could be for example the “Get Info” dialog where you get details about the currently selected song.
Maybe with the rumored switch to ARM processors we can overcome this shortage of processing power and run these two things in different threads.
I was about to complain about something else on Twitter but unfortunately that will have to wait as almost every time I’m trying to upload a video on Twitter it just fails with a non descriptive error message.
Instead of telling me what’s wrong Twitter just gives me a useless message that tells me to try it again until magically the aspect ratio of my video changes. Maybe I should also reboot my computer while I’m at it?
Looking at the requests posted to api.twitter.com/1.1/statuses/update.json I can see that it got rejected because of the aspect ratio. Maybe that would be a more helpful error message?
{
"errors": [
{
"code": 324,
"message": "Aspect ratio too large: Maximum: 3:1, Actual: 396:91 (MediaId: snf:1234567891011)"
}
]
}
I won’t give it another shot.
The AirPods Pro are plagued with issues. There are firmware issues(Sorry for linking to Medium.com) with the noise cancelling and other software (or hardware?) issues resulting in clicking or buzzing devices.
So far I was mostly able to enjoy the latter ones and after getting the left AirPod replaced for clicking noises it was time to replace the right one for buzzing noises. That was easier said than done as the I couldn’t enter the support chat with my serial number for some reason. As usual I’m not the only one with that problem.
Ducking iOS doesn’t let me type “fuck” without changing it but apparently the one time I give Siri dictation a chance because my hands are full of grocery shopping germs it just transforms “can’t” into “cunt” and sends the message.
Being somewhat skeptical of Siri I already added a disclaimer without seeing the result of the Siri transcribed message, a reasonable idea in retrospect. Apparently this is known as SDBNR.
This is how iMessage is greeting me after every reboot. I then have to restart iMessage to see my contacts and chats again. Every single time. Thanks for helping me with that whole social isolation thing, very cool!
I’m not subscribed to Apple Music. My trial period ended over a year ago. Apple Music is completely disabled on this device and anywhere else on my account. Up until a few weeks ago, I’ve never once gotten a single notification for new releases – as it should be. This is the third or fourth notification now. So either Apple fucked something up, or they are doing cool growth hacks. What’s most frustrating about it is the fact that I’m unable to tell which is more likely.
I’ve got a cool new bug a few days ago, completely spontaneously and without updating any software or changing any configuration. After waking my MacBook from sleep, I couldn’t move the mouse pointer with my wireless mouse. The bluetooth connection was there, but the pointer just wouldn’t move. Turning the mouse physically off and on would result in successful reconnection, but even then the pointer would not move. I had to go into Bluetooth settings, remove the device entirely and then pair it again. After this happened for the first time, it was reproducible and happened every single time after waking from sleep. As a result, I quickly learned how to do the entire Bluetooth-Remove-And-Pair dance completely via keyboard shortcuts/controls. It was annoying, but not annoying enough for me to try and see if a reboot would fix it.
Then Apple released a shiny new update. I woke my MacBook from sleep, saw the notification about the update, wanted to click it, cursed because my mouse pointer wouldn’t move again. So I figured this was a good time to reboot and see if the mouse issue would be solved by that. I also figured that I would just save the time to fix the mouse pointer problem – now being a master of keyboard controls, I foolishly thought I could just trigger the update that way. Turns out, the button to actually start the update can not be reached that way. The screen recording above shows me tabbing through all available controls in the Software Update preference pane.
Silver lining: the reboot did fix the mouse pointer problem.
Things I want to do when I download software:
Things I don’t want to do when I download software: