I just block them if they look like they have no reason to follow me. Not sure that is correct way to do it, but it works for me.

The white hood cinch string fell out when I washed my 2025 hoodie and all this time I was hunting for a green string. Thanks to this picture, I'll reinstall the white string I found and stop looking for a green string 😜.

Journeyed to Wisconsin for some cheese therapy. Shullsburg Creamery's muenster melts different and cures ails.

a man wearing a fur hat and glasses is sitting down . ALT: a man wearing a fur hat and glasses is sitting down .

I knew this clip was going places when @aaronfrancis.com double whoahed. Then he tripled down.

Too many French landlords 😅

Thank you for your dedication to this over the years. It exposed me to corners of JavaScript and CSS I would have never stumbled upon on my own. The effort you put into succinct article summaries was much appreciated and I could quickly decide what to read. Long live FSB, it will not be forgotten!

Finally maxed my ESM score.

Also since July 2025 Node coldstarts have gotten faster. When running my benchmark which instantiates a v3 client and makes a service call during init on Node 24, I see it's 50ms faster on init duration and 60ms faster on E2E 🐇.

Good news! That 50ms coldstart latency regression that appeared when using the AWS Javascript V3 SDK on Lambda with Node >= 22 is now fixed. github.com/aws/aws-sdk-...

Update your dependency to v3.1011 to get back in the fast lane. Comparing my patched v3.1006 to v3.1011 shows no delta.

More details on what the node compile cache is if you haven't heard of it before: nodejs.org/api/module.h...

I ran my benchmark overnight to confirm there wasn't much improvement when turning on NODE_COMPILE_CACHE with Lambda Coldstarts. It's less than a 10ms improvement. There may be benefits with larger packages but for my setup (200K zip file) it isn't worth the trouble.

I experimented today with enabling NODE_COMPILE_CACHE to see if it would make Lambda coldstarts faster. I was able to create a .zip file with the cache from a previous run. I verified node used the cache successfully with NODE_DEBUG_NATIVE="COMPILE_CACHE". It didn't reduce the coldstart time 🫠.

Code I'm running. gist.github.com/perpil/ac5b9... It instantiates a STS client and calls GetCallerIdentity in init. (AwsLite has slightly different code but does the same thing).

LLRT v.8.1-beta has the fastest p50 InitDuration by 130ms. But if you measure E2E time from the client (what you should measure), it narrows to 79ms over AwsLite and 118ms over a modified AWS v3 JavaScript client on Node 24. This is likely due to the size of the LLRT binary being ~5MB.

Graph showing lambda coldstart duration over time for recent Node versions and arm64 runtimes with 256-1024 MB memory.

Anecdotally I've noticed Lambda nodejs coldstart latencies trending down but visualizing the improvement using the daily maxday numbers is hard: maxday.github.io/lambda-perf/ I pulled the data and graphed it. Indeed, it's showing a 20-30ms improvement since November last year. Here's nodejs on arm.

Obtaining caller ip address with Lambda FURLs - Speedrun When x-forwarded-for lies

Getting the client ip address when using a Lambda Function Url generally works, but sometimes you get a spoofed one. In this article I cover how to workaround the undocumented mangling Lambda does to the `x-forwarded-for` header.
speedrun.nobackspacecrew.com/blog/2026/03...

For example, if x-forwarded-for is set to 127.0.0.1,205.33.27.32 you get 127.0.0.1 at Lambda. Lambda doesn't seem to mess with other headers that are comma separated, just x-forwarded-for.

I discovered that if you use Lambda furls, the x-forwarded-for header is truncated to the leftmost value. If you front your furl with CloudFront, the ip in that header is spoofable. CloudFront appends the viewer ip to the value of x-forwarded-for. Workaround is: github.com/aws-samples/...

TIL I was still using http 1.1 to connect to my api which supported http3. Because http3 is still kind of broken in Firefox: bugzilla.mozilla.org/show_bug.cgi... and when you enable http3 in CloudFront using the CDK, it disables http2. github.com/aws/aws-cdk/...

TIL you can get edge location in your CloudFront Functions. docs.aws.amazon.com/AmazonCloudF...

Hello darkness my old friend. I just updated to JQuery 4.0.0. Ready for 10 more years of $.

Just turned it on, TIL too, thanks!

The places where nexus share breaks the thread into posts always seems unnatural. Consider breaking it on sentence boundaries or something more organic.

Fwiw, when I was in this situation, Fi support did some things but nothing changed and ultimately I had to wait 7 days before I was able to resubscribe. I didn't lose my storage however, it was still there when I resubscribed.

They really do need to do this instead of letting Fi takeover the subscription. I causes problems like when you downgrade Fi and lose a benefit, you can't resubscribe (i.e. Google One) for 7 days until Fi releases the hold. And while you can't resubscribe they tell you you will lose your storage!

PSA: There is a performance penalty when using named exports with ESM import vs. require on built-in node modules. This is why the AWS JavaScript V3 SDK has 50 ms slower Lambda coldstarts on Node 22+. Some notes here: github.com/aws/aws-sdk-...

Look, the plating and bread choice leaves room for improvement. But the flavor of my latest Persian-American cuisine; the sumac avocado toast slaps.

After many exasperated console.log's I looked at the docs and discovered CloudFront functions don't run on responses with a status code >= 400. So my edge metrics only work on successful requests. docs.aws.amazon.com/AmazonCloudF...

Seeing some Dr. Suess bird in my latte this morning

When I tried in us-east-2 I got an error that it wasn't enabled for my account. Both via cloudformation and the console.