ShortFuse

Since you've gone, I've been lost without a trace
I dream at night, I can only see your face
I look around, but it's you I can't replace
I feel so cold, and I long for your embrace
I keep crying, baby, baby please
Oh, can't you see
You belong to me?
How my poor heart aches
With every step you take?

I understand the full lyrics, but most songs generally default to romanticism. If you're not paying attention it's easy to misinterpret.

1F919 - Call Me Hand

https://www.unicode.org/charts/PDF/Unicode-9.0/U90-1F900.pdf

I remember this actually: Ted Cruz kisses his daughter... it doesn't go well

I have just dumped code into a Chrome console and saved a cert while in a pinch. It's not best practices of course, but when you need something fast for one-time use, it's nice to have something immediately available.

You could make your own webpage that works in the browser (no backend) and make a cert. I haven't published anything publicly because you really shouldn't dump private keys in unknown websites, but nothing is stopping you from making your own.

That's what NodeJS and Deno are.

The point of the browser support means it runs on modern Web technologies and doesn't need external binaries (eg: OpenSSL). It can literally run on any JS, even a browser.

Just going to mention my zero-dependency ACME (Let's Encrypt) library: https://github.com/clshortfuse/acmejs

It runs on Chrome, Safari, FireFox, Deno, and NodeJS.

I use it to spin up my wildcard and HTTP certificates. I've personally automated it by having the certificate upload to S3 buckets and AWS Certificates. I wrote a helper for Name.com for DNS validation. For HTTP validation, I use HTTP PUT.

Pippi Longstocking

I mean, you can find 70s punk images just like this. I'm sure some are already great-grand parents. Nancy and Sid are from 1977:

Windows 10 and it's not a good idea

Even line-height in CSS3 is draft. Saying no drafts should be implemented is a ridiculous standpoint: a standpoint not even Firefox aligns with:

Standardization requirements for shipping features

What evidence is necessary will vary, but generally this will be:

W3C - the specification is at the Candidate Recommendation maturity level or more advanced; shipping from a Working Draft or a less advanced specification requires evidence of agreement within the working group that shipping is acceptable

https://wiki.mozilla.org/ExposureGuidelines

But keep moving those goal posts.

What? They all have W3C specs. Firefox just chose not to implement them.

• https://www.w3.org/Graphics/Color/Workshop/talks.html
• https://www.w3.org/TR/appmanifest/
• https://wicg.github.io/shape-detection-api/#barcode-detection-api
• https://www.w3.org/TR/nfc/
• https://www.w3.org/TR/accname-1.2/#computation-steps
• https://drafts.fxtf.org/css-masking/#the-mask-border

You think you're trashing Chrome, but you're trashing Firefox instead.