perpil

I modified the script to start collapsed. Code is in this issue if you would like to try it: https://github.com/twalichiewicz/HNewhere/issues/5

Tampermonkey isn't better than using a Chrome extension, but it's less friction for a developer to build and distribute a cross browser script. If they build it as an extension, they need to target multiple browsers and get it deployed to the Firefox/Chrome web store.

This is slick. 2 things.

1. If you name your script with the extension .user.js it is easier to click on to automatically install at least with tampermonkey. 2. When I went to this link from the main page, on mobile I had to scroll to the right to see the (-) to minimize because the sidebar was too large: https://elizabethtai.com/2026/06/10/substack-writers-you-nee... It may make some sense to start minimized so I can read the article first, but I can easily modify the script to do that.

I first thought this was some spin on May the fourth be with you. As in how Yoda might say it.

This page says bundle size is 14MB: https://blackboard.sh/electrobun/docs/

Consider removing this from the landing page if you want to be taken seriously: "we are in the pursuit of greatness. fueled by caffeine, nicotine, and pure chaos"

Agreed, maybe a forest fire or lightning strike might have made it more obvious that charring preserved. Charcoal in a campfire could have easily disappeared in the next fire.

They do give Leonardo a lot of credit for a single sentence, but it may be the first documented instance of this charring technique.

This is very thorough, but I have a few things to add if you are using Node 22. I benchmarked Node 22 earlier this year using something similar to the light benchmark. https://speedrun.nobackspacecrew.com/blog/2025/07/21/the-fas...

I found that Node 22 had ~50ms slower coldstarts than Node 20. This is because the AWS Javascript V3 SDK loads the http request library which became much heavier in Node 22. This happens on the newly released Node 24 as well.

I recommend that if you are trying to benchmark coldstarts on Lambda, you measure latency from a client as well. The Init Duration in the logs doesn't include things like decrypting environment variables which adds ~20ms and other overhead like pulling the function code from S3. The impact of this manifests when comparing runtimes like llrt to Node, the Init Duration is faster than Node, but the E2E time from the client is actually closer because the llrt bundle size is 4-5MB larger than Node.

Its predecessor (mkdocs material) supported blogs via a plugin and rss feeds via a mkdocs plugin (https://guts.github.io/mkdocs-rss-plugin/). I don't believe it supports blogs yet according to this: https://zensical.org/compatibility/#phased-transition-strate... but will in the next phase when it supports plugins.

It doesn't support loading content from a database that I'm aware of, it uses markdown files on disk as input.

My read of this: https://www.alaskaair.com/content/about-us/customer-commitme... indicates you should be able to get a discount code of $50 if your flight was delayed 3 hours if you ask them.

This is not about the AWS Console. It is talking about the customer's site hosted on CloudFront. It is possible to cross wires with user sessions when using CloudFront if you haven't set caching granular enough to be specific to an end user. This scenario is customer error, not AWS.

Also see https://runme.dev for a similar approach or https://speedrun.cc if you'd like it to work straight from GitHub markdown.

The fact you've copied screen.studio so closely leaves a bad taste in my mouth. On the landing page you apply formatting in Google Sheets, just like screen studio does. It's ok to be inspired by screen studio but remember they are mostly a solo dev too so try and be more original.

Not OP but was there 15 years (left Dec 2021) and surprised I wasn't aware of this. I was only aware of a few tools that acted like chatbots to automatically gather context or take action from chime/tt/alarms.

When I was at AWS, I built something so I could run things straight from the wiki. Think cloudwatch queries, aws cli commands etc with user inputs but without all the setup of securely getting the right credentials and formatting inputs. I've rebuilt to run stuff straight from GitHub. Here's it invoking a lambda function straight from a github wiki with user input in 4 lines of code: https://speedrun.nobackspacecrew.com/index.html#invoking-an-...

The video on your landing page is too long for my tastes. A 1-5 minute video quickly showing the features would have more impact than your 20 minute walkthrough attempting to show every detail. The 20 minute video is more suitable for the documentation.

I did something like this but it helps you build exact command lines or interact with AWS straight from your GitHub markdown. As a bonus, it very easily lets you prompt the user for inputs and pivot between different accounts. https://speedrun.cc

Servpro doesn't fix heaters, they mitigate fire damage. They came expecting to fix fire damage, not a heater.

Typo on the menu: Acitvity->Activity

I do something like this with https://speedrun.cc except it runs in the browser on top of your markdown in GitHub. This lets you prompt for inputs and run JavaScript and use a toolbar to context switch. For command lines it copies the command to the clipboard so you can run it.

Neat, you might also look at https://speedrun.cc for ideas. It's a slightly different space, it's markdown to wrap tools with UI's instead of to plot things, but the way I enable you to prompt the user and run little bits of javascript might be of interest to you.

The Mom Test teaches you how to ask the right questions to make sure potential customers actually have a need for and will pay for what you are building vs. lying to be polite. The Mom Test: How to talk to customers & learn if your business is a good idea when everyone is lying to you https://a.co/d/8rxZlJ7

Another benefit of BYOK is it simplifies the implementation. You don't need to spend as much time protecting against the attack vector where they rack up a big bill against your key.

DynamoDB also makes for a nice fine grained secrets manager with their new table resource policies: https://speedrun.nobackspacecrew.com/blog/2024/06/27/using-d...

I like the integration with slack and the inline execution of steps. I've been working on a similar product with https://speedrun.cc but it just piggybacks on GitHub markdown and most of the execution is done via a deeplink. Reach out if I can help, I've been messing around in this space for awhile.

A workaround for some of the limits of presigned urls like not being able to specify a max file size is to front your uploads using CloudFront OAC and CloudFront Functions. It costs more (.02/GB) but you can run a little JavaScript code to validate/augment headers between your user and S3 and you don't need to expose your bucket name. https://speedrun.nobackspacecrew.com/blog/2024/05/22/using-c...

Presigned post lets you set content-length-range: https://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-authen... You can specify content length on presigned PUTs, but it needs to be set as a header and added to the signed headers for SIGv4. It can't be set as a query param.

> Can you create a size limit on the pre-signed URL?

Yes, if you use the POST method you can set the content-length-range property in your presigned URL form inputs to limit min and max bytes. https://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-authen...

The best part of SPL is you get full digital access to the O'Reilly public library, you don't even need to place holds. Most tech books I've ever needed are a search away. https://www.spl.org/books-and-media/books-and-ebooks/oreilly...

"we cannot confirm that no other such instances occurred". I'd like to understand this more. Do they 1. not have a fingerprint of what the exploit looked like because it was indistinguishable from customer behavior? 2. Not have logging necessary to audit this? Regardless, with the added monitoring to detect suspicious activity, do they also have the logging to see everything a bad actor did if there is a new exploit?