My brain is having a real hard time accepting that "die" is falling out of use and that "a dice" is correct English.

> You can provide this information by replying to this message.

> From: no-reply-aws@amazon.com

🤔

Is it just me or do 99% of login forms with a "remember me" option still forget me the next day. It's gotten to the point where I don't even bother clicking it anymore.

angry at browsers 

@LionsPhil I would hope that they are doing this the "right" way where they keep the old version around until you restart into the new one. That way you can continue opening tabs.

For example this issue doesn't occur on NixOS because the new Firefox is installed into a new path. It does occur on most distros since the Firefox installation is updated right underneath a running Firefox so there isn't much Firefox can do but not crash and report a nice error.

TIL in SQL `TIMESTAMP WITH TIMEZONE` is in fact just a timestamp.

On the bright side this is the datatype I actually wanted. Unfortunately I was using `TIMESTAMP WITHOUT TIMEZONE` because I didn't want to store the timezones.

AFAICT the only difference is how they are parsed on input and output. Depending on the type any of converted to UTC, assumed to be UTC or assumed to be in the connection timezone.

For extra confusion TIME types can actually store a timezone, but that is a whole-nother set of bugs

It looks like Google Search Console lost a date somewhere:

Linking page: blogsurf.io/all
Last crawled: 1969-12-31

sumologic.com: By default the JSON field called "timestamp" containing a UNIX timestamp in milliseconds will be used as the time of the log message.

Me: Sounds reasonable.

sumologic.com: Unless the JSON object contains another sequence of bytes that looks like a timestamp occurs earlier in the JSON string in which case it will be used instead.

Me: Excuse me what?

So if you are using sumologic you better be careful not to log any timestamps that aren't the current time or sort your JSON fields 🤢

Service managers that pass sockets to daemons are incredibly cool.

1. A script is stuck. IPFS is probably hung.
2. Navigation to IPFS webui hangs.
3. Restart IPFS. Graceful shutdown fails, it gets SIGKILLed.
4. Pre-start config fails due to an IPFS bug.
5. Manually start IPFS daemon to fix state.
6. Restart IPFS again.
7. Browser successfully finishes webui load.
8. Script finishes successfully.

So go-ipfs is trash, but I just had a hung process ungracefully restarted without any clients "noticing".

sunlife.com just asked me to enter my password in digits over the phone. I guess they aren't storing passwords securely 😢

GitHub doesn't believe that Linux developers can have emoji.

```
function isEmojiSupported() {
const onWindows8 = /\bWindows NT 6.2\b/.test(navigator.userAgent);
const onWindows81 = /\bWindows NT 6.3\b/.test(navigator.userAgent);
const onFreeBSD = /\bFreeBSD\b/.test(navigator.userAgent);
const onLinux = /\bLinux\b/.test(navigator.userAgent) && !/\bAndroid\b/.test(navigator.userAgent);
return !(onWindows8 || onWindows81 || onLinux || onFreeBSD);
}
```

My dentist: You should use a softer toothbrush.
Also my dentist: Attacks my mouth with a steel pick.

I like how the Canadian Revenue Agency website asks you a different "security question" each time you login so that you can break into someones account if you know their mother's maiden name, their niece, their favourite movie OR the street that they grew up on!

Such security, many safe.

It boggles my mind that GitHub Actions pages don't have a link to the originating PR.

They even **show you the PR number** but provide no link. 🤦

Show older
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!