Recent submissions

Comment · 1 year ago
Whitelisting these hosts mean they become extraction vectors for prompt manipulation. In fact it’s mentioned in the grant parent’s article at the end. So yes, it takes a while to do this right.
Comment · 4 years ago
Comment · 5 years ago
Comment · 5 years ago
They probably mean some access to production servers where it might be scanned in memory or otherwise grabbed using debug tooling. Making this possible for 0 people will be challenging and at the least add a lot of complexity.
Comment · 5 years ago
Comment · 5 years ago
Haha, this is hilarious in a very sad way. Can only imagine how the internal conversation about such an implementation went :).
Comment · 5 years ago
True, but you do want to test the emergent control system.
Comment · 5 years ago
Comment · 5 years ago
Comment · 5 years ago
Ha, very nice!

To clarify: to reverse the list, one would only have to swap the HEAD and TAIL pointers of the base structure.

Comment · 6 years ago
The work-around for the first issue might work well in practice, but due to asymmetry of tcp streams, is still open for a race where the server will idle-close a connection while a new (non-idempotent!) query is just in-flight.

The correcter solution would let the client manage the idle-timeout and disconnect once reached. Depending a bit on how controlled the client is, this might be a good or bad idea.

Note that this problem is very generalizable to http (1) upstream servers. If you need to support non-idempotent requests and want persistent connections to your upstream, it's not a good idea to have the upstream manage the idle timeout (and disconnect if reached).

In practice, I would have the client manage an idle-timeout of 30s, and server of 40s as an extra protection against misbehaving clients.

Comment · 6 years ago
In my experience, "logic wants to be code, and not data". Ie it's a dangerous (although sometimes necessary) step to move this into the data domain. Did you encounter any difficulties with missing source control, being able to use debugging tools, etc?
Comment · 6 years ago
For those wondering as well, at 10b quarterly revenue, 10m monthly is ~.3% of all AWS revenue.
Comment · 6 years ago
It's fairly nice but indeed rather implicit. I would kill for a postgres setting where feeding (an evaluated) NULL to the where clause logs a warning. This would force developers to coalesce (at least on top level) and think about the null case when applicable.
Comment · 6 years ago
Not for the internship position unfortunately

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton