Aside from future-proofing, can I ask why this is important? I believe you that it is, I’m just curious.

This is hilarious

Love to see MBMBaM!

Love to see The Dollop!

It’s very optimistic to think people will be able to describe what they’re going to do before they do it. I find things rarely go exactly as planned and my commit messages usually include some nuance about my changes that I didn’t anticipate.

Got it! Are they renumbered chronologically? Like if my 11 was created before your 11, would yours be the one that’s renumbered?

Commit IDs are only local anyway.

Whay do you mean by that?

Thanks!

Wow I almost forgot the original name! I was skeptical it would catch on, as name changes are very hard, but fortunately it was very early on and I bet a lot of other people have forgotten as well.

I don’t understand what this is, can you explain? Apologies if it’s obvious.

I run a “public” instance with basic auth so I can use it from anywhere (phone, work). I’ve made my instance my default search engine everywhere. (I know basic auth is not the most secure but I wouldn’t even really care it other people used my instance; I just don’t want it hammered.)

Make sure to put the word spoiler on the first line after the colons for it to get rendered correctly.

Like this

::: spoiler screenshots incase it gets deleted
Your images here
:::

Looks like this

I’ve been really impressed by Dart as a programming language. I’ll admit I don’t have a breadth of knowledge, but coming from C# I feel right at home, and it has a few extra neat tricks that C# is picking up in return (like empty list syntax and the spread operator).

I’ve been trying to explain to someone recently why rebasing and force pushing their feature branch has no benefit when we use a squash commit strategy for merging to main.

While you’re 100% right, is there anything wrong with this approach? Sometimes I like to keep by personal branches clean, especially before I open a PR.

Here’s one for Wear OS / Pixel Watch.

https://play.google.com/store/apps/details?id=com.watchfacestudio.az261jsoncodewatchface

EDIT: And a terminal one.

https://play.google.com/store/apps/details?id=com.watchfacestudio.awfterminal

Working on it!

I think if they were using a private IP, there wouldn’t really be a joke. Of course the router can resolve an IP in its network. The joke is that they’re using their public IP from inside their network, and when the request gets the router, instead of resolving externally, it resolves to the public IP of the router itself.

If the router supports hairpinning, the IP request can be resolved locally.

The domain name lookup would be a different issue and could potentially need to be resolved externally, but the router’s DNS cache should be able to answer eventually.

Because the title mentions having a domain, I guess.

This is based on a classic saying, “you scream, I scream, we all scream for ice cream”. In case you’re not a native speaker or it’s not obvious from text, the saying is based on the fact that “I scream” and “ice cream” sound similar, so it’s a bit of a pun. However, without the last part of the saying which references “ice cream”, it just sounds like there’s a bunch of screaming, which is pretty terrifying!