HN user

dochne

59 karma
Posts0
Comments17
View on HN
No posts found.
Ruby 3.4.0 2 years ago

Experienced teams know to be careful and sparing with its use.

I had one of the predecessors to this (the Jelly 2) as one of my strategies to cut down on smart phone usage.

It was a nice idea (as it introduced pain points of using it as a distraction device), but the battery life ended up being abysmal to the point that I couldn't trust it to complete a day. Having a tiny smart phone and then having to take a battery pack for it was absurdity.

It also led me to appreciate how much I'd come to rely on always having a good camera in my pocket. The picture quality was poor enough that the photos would leave me feeling genuinely quite sad.

If you're reading a PR diff on GitHub you can get it to ignore whitespace diffs by adding ?w=1 to the url - complete lifesaver in this kind of situation.

It still remains a mystery to me why browsers felt they should "fix" this server misconfiguration.

It's particularly vexing to me as the main reason that people end up with misconfigured servers at all is because after they've configured their new cert (incorrectly) their web browser gives them a tick and they think they've done it right - after all, why wouldn't they?

My understanding is that Postman unfortunately pulled the same thing lately, so that's unfortunately a no-go for you.

I've previously had good experiences with Paw (now RapidAPI) - https://paw.cloud/, but given that they are closed source and have started giving away the software rather than charging for it, I'm not filled with optimism they won't do a similar rug pull.