Readit Newsethomson commented on Speedbump – a TCP proxy to simulate variable network latency github.com/kffl/speedbump... · Posted by u/sph
This is delightful and I can't wait to try it out. Right now, the libgit2 project (https://github.com/libgit2/libgit2) has a custom HTTP git server wrapper that will throttle the responses down to a very slow rate. It's fun watching a `git clone` running over 2400 baud modem speeds, but it's actually been incredibly helpful for testing timeouts, odd buffering problems, and other things that crop up in weird network environments.
I'd love to jettison our hacky custom code and use something off-the-shelf instead.
They are baguettes. They’re eating at the Copper Kettle and these look like their ‘breakfast baguettes’
Yes, that’s definitely the Copper Kettle.
More interesting than the food, though, is the background. Those who aren’t familiar with Cambridge will see King’s College in the background, across the street, which many may know from the BBC’s Carols from King’s.
It's a word with multiple meanings and one of them is a type of dwelling. Which other meaning do you think is more appropriate given the context?
There’s no confusion about it referring to a dwelling. The confusion is about the _type_ of dwelling.
To quote Wikipedia:
> In American English, "cottage" is one term for such holiday homes, although they may also be called a "cabin", "chalet", or even "camp".
In other words, calling a multi-million pound property a “cottage” would rankle an American ear.
I understand that bu Vercel KV is almost 2x more expensive than Upstash. Even the vercel/kv package is just a wrapper for upstash/redis - I mean what is the benefit of using Vercel KV instead of Upstash? What DX is improved?
Upstash offers a nice UI and easy integration with edge functions and lambas functions. It's the same with neon database and cloudflare r2. The only plus value I see is the centralised dashboard. Paying 2x for a single dashboard?
Product Manager for Vercel's storage products here. Today we announced three new storage products in beta; they're based on infrastructure that are provided by partners. There's a lot that goes in to pricing products -- and our products are distinct from our partners' products. We have different roadmaps and will introduce different features as we continue development. So I don't love to make too many comparisons between apples and oranges.
But I suspect that you might be comparing Upstash's per-command pricing for _regional_ requests ($0.20 per 100k) to Vercel KV's? In fact, Vercel KV is multi-region, so the more apt comparison is Upstash's pricing for _global_ requests ($0.40 per 100k).
ethomson commented on Is the Living Computer Museum dead? pcjs.org/blog/2023/02/16/... · Posted by u/ingve
I was fortunate enough to go in 2019, pre-covid, while I had a day off in Seattle. It was a great museum, and I’m disappointed that I won’t be able to go back.
I tweeted a bunch of photos: https://twitter.com/ethomson/status/1109880552360951810
ethomson commented on Show HN: Send a GitHub webhook to a private URL github.com/openziti-test-... · Posted by u/qrkourier
The proxy idea is interesting too. Does a webhook proxy entail a polling model for events? That is, does the private server have to poll the proxy to receive the webhook? I wanted the GitHub event to push to trigger actions on the private server.
No - your local server will still listen for webhooks, but they'll come from the proxy's client software.
Basically, you set up your GitHub webhook URL as the proxy server (for example, smee.io). Then you run a client on your local machine that connects to the proxy server. When a webhook is fired, it will be sent to the proxy, then delivered to the connected client, which will then pass it along as a webhook to whatever machine you've configured.
There's disadvantages to having all this stuff running, of course, so I think that handling this at the networking layer instead of putting a proxy just for webhooks into place is an interesting strategy. Certainly, it sounds like the right solution if you're already using OpenZiti.
ethomson commented on Show HN: Send a GitHub webhook to a private URL github.com/openziti-test-... · Posted by u/qrkourier
Neat stuff - certainly this problem crops up quite a lot where an internal server needs to get GitHub webhook data.
In the past, I've had good luck using a webhook proxy. I've mostly just used https://smee.io/ which is simple and lightweight although seems to be mostly abandonware at this point. I dockerized it so that it could be used in a Kubernetes cluster, which was very useful for my GitHub Actions build cluster: https://github.com/ethomson/smee-client
There's also Hookdeck, which I haven't used in production, but have played around with, and it seems conceptually the same, but can be made more Enterprisey. Whether that's a bug or a feature is probably up to you.
HN has connected me with insightful and over-the-top competent people; I’m happy to be considered one of the gang. To the many who’ve helped me understand things from time crystals to homotopy theory, my deep thanks!
While I’ve tiptoed away from many turbulent scenes, I remain curious (just discovered that a biocide used as a paint additive to kill mildew is an ingredient in my shampoo). Still hacking & coding (handful of rasp pi’s), still sewing (finished an appliqué quilt last week), and still making these odd onesided shapes.
From a across the ether and across the decades, my warm wishes to those who’ve made this forum an inviting and occasionally inspiring place!
-Cliff (on a cloudy Thursday morning in Oakland)
At some point, I stopped trying to drag my pre-teen schoolmates along with me, but I still have my original hardback and re-read it regularly.
Your book taught me many things - perhaps most importantly, that one can educate about complex topics in engaging and understandable ways. And now I’ve landed in a job that focused on security.
One of the things that I’ve been doing in this job is, well, trying to educate about complex topics in engaging and understandable ways. I’ve thought about your book in every blog post I’ve written lately.
Thanks, again.