No, but our oven door did this one night.

"as collosal a collection of excuses and projection as the Court has seen in 25 years on the bench."

I stopped using Skylight because it was redirecting me to the OAuth page in a web view. So if I wanted to use a saved password Android would prompt and say "do you want to share your password with Skylight?" They fixed this and now open it in a custom tab.

We switched to using front spoon and back spoon for this reason.

I love a good theme. Our build system all uses train terminology.
Artifacts go in Depot.
Deploys go out on the Train.
Third-party deps are pulled through a caching proxy called Ballast (for build stability).
A new tool for checking Bazel build determinism is called Derail.

This is my personal favorite method for counting ranked choices.

Yeah, we got the PHEV Pacifica and it's been great for us. We always plug in at home. We usually only fill the gas tank half way because it eventually wants to run the engine to burn the old gas if you haven't filled up in a while.

Something similar was happening to my Android phone and I had to turn off IPv6 in the router.

I just scored 7,220 on a game of at://2048.
Think you can do better? Join in on the fun with @2048.blue.

I'm gonna go prompt-inject myself a new minivan!

The server math is the same either way. It would be stored in the database as a second-precision timestamp even if you chose from just a few options.

If you buy your own domain (hank.green, for example), you could create multiple accounts on separate subdomains. @hank.green for your main, @science.hank.green for science facts, @pelicans.hank.green, etc.

Did you sing them the "Million Dollar Idea" song? How can they say no to that?

Hash all of the SVG files and put them in a content-addressed cache. Create a {name: svgDigest} JSON file for that set of icons, and put it in the CAS as well. Bake the digest of that mapping into the icon JS. This is basically what we do for all JS bundles on lucid.app.

How much do you care about the extra round trip for an intermediate lookup vs the bytes saved on shipping the whole map? What if the whole lookup map can be cached forever (until an icon changes)?

Of course, if you expect the client to load a bunch of icons that start with the same letter, then keeping those in the same lookup map might be better.

You could do the same, but hash the names and use the first N nibbles of the hex digest to get a roughly even distribution of icons in each map even if a lot of the names start with the same letter.