ShortFuse

joined 1 year ago
[–] ShortFuse@lemmy.world 1 points 2 weeks ago (1 children)

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.

[–] ShortFuse@lemmy.world 1 points 2 weeks ago (3 children)

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.

[–] ShortFuse@lemmy.world 11 points 2 weeks ago* (last edited 2 weeks ago) (5 children)

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.

[–] ShortFuse@lemmy.world 12 points 4 weeks ago (1 children)

Pippi Longstocking

[–] ShortFuse@lemmy.world 5 points 1 month ago

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:

[–] ShortFuse@lemmy.world 4 points 2 months ago (1 children)

Windows 10 and it's not a good idea

[–] ShortFuse@lemmy.world 2 points 2 months ago* (last edited 2 months ago) (1 children)

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.

[–] ShortFuse@lemmy.world 3 points 2 months ago (5 children)

Firefox, unfortunately, has been lagging behind. Safari is close to surpassing Firefox if they haven't already. Safari really made a big shift for actually implementing web standards around 16.4.

  • No HDR - relevant for me because I mod PC games for HDR
  • Dropped PWA on desktop - even Apple went full 180° and embraced it now on Mac OS X. Chrome really gets a good push from this from Microsoft constantly helping push more app manifest stuff since it appears one of their goals is to render more things over Edge PWAs (eg: like the title bar), and resort less to having to use electron.
  • No masked borders - can't do custom element borders like corner cutting or perfect squircles. Rounded edges only

Chrome is still the absolute best for accessibility. Neither Firefox nor Safari properly parse the aria labels when it comes to how things are rendered. Chrome will actually render text in accessibility nodes as presented on screen (ie: with spacing). Safari and Firefox only use .textContent which can have words beingmergedwhentheyshouldn't.

Chrome also has Barcode and NFC scanning built right in. I've had to use fake keyboard emulators for iOS. Though, Chrome on Mac OS X also supports it. Safari has native support for Barcode behind a flag, so it'll likely come in the future. Barcode scanning is still possible with Firefox through direct reading of the camera bitmap, which is slower but still good. There's no solution for NFC for Safari, but if Chrome ever comes iOS, that would possibly be solved. I believe Face Detection is similar, but I've never used it.

view more: next ›