Founder of https://httptoolkit.com (@httptoolkit.com), Node.js core collaborator, tech speaker, drummer, mountain biker and dad.
š¬š§/šØš¦ living in šŖšø

@pimterry.fyi
Founder of https://httptoolkit.com (@httptoolkit.com), Node.js core collaborator, tech speaker, drummer, mountain biker and dad.
š¬š§/šØš¦ living in šŖšø
š
I'm building a new bicycle! Mixed gravel/bikepacking/XC bike, piece by piece (over a month or two). Step 1: custom titanium frame just arrived š
For the EU at least, they have now regulated a bunch of this: www.autonext.co/tips-guides/.... Does that cover it? Applies to all newly built fast chargers already, all existing fast chargers from 1 Jan 2027.
airdrop fully reverse-engineered! works flawlessly on my framework laptop
If you'd like to contribute to an oss project, don't focus on creating PRs. Help the maintainers triage issues and review existing PRs. Test beta releases, and give feedback about new APIs and features. Join the community and be around to help others. They need your care way more than your code now.
"On This Day" memory: Oct 4, 2014 - "WeNode", the first (unofficial) #NodeConf Barcelona. 1 day, 2 tracks, with @pimterry.fyi @rreverser.com @krasimir.bsky.social and so many more amazing folks. We had JS cake and @gorhgorh.bsky.social with his Cat Bot laser kits for people to build. What a day ā¤ļø
Honestly I'm not really involved on the Node side at all here, it's been years since I really cared about logging, but the contrast is spectacular. In the meantime, astonishingly Loglevel's still kicking! 23mil downloads last week and climbing.
I released github.com/pimterry/log... back in 2013. IE6 & 7 had no console.log, others had inconsistent (even intermittently available!) APIs, and basics like real log levels were impossible.
Very cool to see Node discussing a fully featured built-in logger, 13 years later. We've come a long way ā¤ļø
Node.js going to the moon at @nodeconf.eu š
If you're using custom system CAs on Android for TLS - whether that's for HTTPS debugging, ad blocking or local testing - there's trouble brewing. Let's talk about the latest Android 17 changes and how to keep things working:
nobody else has the steel moral core to tell you the truth in release notes
In Node.js we have a "canary in the gold mine" tool, which does the equivalent for Node changes - runs the build & tests of popular JS modules with the new Node version to see if anything breaks: github.com/nodejs/citgm
Worrying about post-quantum key exchange now is all very sensible and good, but just wait until the smart device industry realises it needed to ship PQ update verification years ago...
I know we're all worried about quantum computing breaking encryption etc etc, but on the bright side: isn't it going to be cool when every old locked-down IoT device that only accepts updates from a server that no longer exists can be resurrected by faking the cert on your own personal quantum box?