Recent submissions

Comment · 29 days ago
Comment · 3 months ago
https://www.404media.co/footage-shows-cop-stalking-woman-he-...

So do we need to wait for abuse with this specific piece of technology in order to be concerned?

Comment · 6 months ago
Comment · 1 year ago
Absolutely, I do this at $dayjob to update feature flags and refresh config. Your code just needs to understand that such execution is not guaranteed to happened, and in-flight requests may get interrupted and should be retried.
Comment · 1 year ago
Comment · 1 year ago
> I won’t get sucked into the session ID vs. JWT argument, but honestly, using JWTs in cookies is a win because you don’t have to fuss with storing session data on the server.

Okay, but then you implement storage of the refresh token and build this bespoke JWT re-issuance logic. So where's the win here? Just use sessions.

Comment · 1 year ago
Comment · 1 year ago
> Yes it is. But the the 1st amendment does not say that any speech can have zero consequences for you.

The Government taking action against a citizen for voicing opinions it does not agree with falls pretty clearly into what the 1st amendment covers. This is not a "yelling fire in a crowded theater" type scenario where speech is being restricted for the benefit of many.

Comment · 1 year ago
> Their profit margin is 5.5%.

5.5% of what, dmm?

https://www.healthcaredive.com/news/unitedhealth-unh-2024-re...

> the Minnesota healthcare behemoth reported adjusted profit of $25.7 billion — an all-time record.

Comment · 2 years ago
Does AWS need to build anything on the site as part of this deal, or are they simply leveraging the power added to the grid in their existing us-east-1 footprint? The distance from Ashburn is too far for this to be an extension of a region.
Comment · 2 years ago
Comment · 4 years ago
> I mean, you didn't even consider implementing a simple fetch of an already cloned repository in your mirroring server code. So yeah, I'd argue that the bad faith part is actually justified.

https://github.com/golang/go/issues/44577#issuecomment-11378...

> We did consider caching clones, but it has security implications and adds complexity, so we decided not to. It is certainly not trivial to do and not something we are likely to do based on this issue.

Drew continues to act as though he is always correct, and any viewpoint that isn't his is just moronic. I've repeatedly seen this behavior from him in multiple venues over the years, and I'm happy to see the wider community start calling this out as childish.

Comment · 4 years ago
There's a _lot_ of assuming happening on this post so far. My understanding was the Twitter account previously had different handles, including her real name. I don't think that level of sleuthing requires internal access, using old/archived tweets can unmask the account.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton