Corporate support can be a big deal.

In a previous life, I routinely blocked anything from a free cloud host or cert provider. There was rarely a business justification for accessing a site or service hosted on DigitalOcean or signed by LetsEncrypt. Sure, get an SSL cert and host for your personal project - so I wasn’t mad at the services - but it was a signal that the endpoint was not trustworthy beyond the TCP packets.

I suspect that AWS/GCP/Azure has made that much harder.

That’s pretty cool. Gets the point across - and the reason and results of why it matters to report instead of ignore. Kudos to your team.

Hah. Neat!

For pedantry…

My understanding was that en-dash was a range, and em-dash was a change in topic or a parenthetical, so I’ve been using the wrong one but for the right reason. This may be an American style distinction, though. Time to jump into a new rabbit hole.

I wonder how many em dashes are real vs interpreted.

I love an em-dash, but I have never typed one on purpose; they are all just two minus in a row and I use them wrong – with a space around (*inspect source to see that lemmy translates for me). I abuse them like I abuse semicolons. They are a typographical tick that indicates a pause or pivot when I translate my thoughts to text.

I can imagine a human manuscript editor turning punctuation like a comma into an em-dash when it makes sense, but I can’t imagine a developer ever specifically typing out one – with the need to either know or look up the unicode for it. The only relevant place would be a comment, but even then IDE’s are not generally known for their tendency to replace typed characters with something else.

Maybe some tool in the pretty-print/code-formatter ecosystem added that as a feature? But var-- is so common that I can’t imagine that’d be a good idea, even in a comment.