Ellipsis753

Joined 13 years ago

Karma
519
Submissions
289
Member since
Mar 24
www.ifnotequal.com
View on Hacker News

Recent submissions

Comment · 4 months ago
Yes! JWTs in the browser are a total pain. You need a way to revoke them (when a user is fired, etc). Or you need to make them crazy short lived (5 minutes). Users need to stay logged in without the tab open for a lot longer than 5 minutes, so you need a way to make that work. They tend to be really large, which slows down your load times a lot due to TCP slow-start and people just having weak upload speeds. And they can easily get too large to store as a cookie. Also, people forget that anyone can read the data stored in the JWT. They just cause more problems than they solve and there's a lot of edge-cases and footguns.
Comment · 10 months ago
Old links to your site might still be http - HSTS prevents that request being in the clear. Also, if you have a man-in-the-middle attack, it doesn't matter if you return a redirect or not as the attacker has already replaced your site with a phishing attack instead of a redirect. HSTS prevents this.
Comment · 10 months ago
It should be able to factor 15.
Comment · 1 year ago
I was amused but unsurprised to see that this article was deleted when I looked it up...
Comment · 1 year ago
Looks like you were rate limited at the end. They don't rate-limit britishairways.com which is a SNI that you can always access. Lolz.
Comment · 1 year ago
It does sound like each server is its own process. I think you're correct that it would be a little faster if all games shared a single process. That said, then if one crashed it'd bring the rest down.

This is one of those things that might take weeks just to _test_. Personally I suspect the speedup by merging them would be pretty minor, so I think they've made the right choice just keeping them separate.

I've found context switching to be surprisingly cheap when you only have a few hundred threads. But ultimately, no way to know for sure without testing it. A lot of optimization is just vibes and hypothesize.

Comment · 1 year ago
Great article. Not understanding the hate.

I think the jist of it is, you probably have sufficiently low requests/second (<1000) that using postgres as a cache is totally reasonable - which it is. If your hitting your load tests and hardware spend, no need to optimise more.

Comment · 1 year ago
Is this saying that intel will support _only_ 512 instructions? (And not 256).

Or that it'll support _both_ 256 and 512 instructions going forwards (and stop doing the nonsense where some cores support 512 and others don't?)

Comment · 1 year ago
This is how most of the top of leaderboard works.
Comment · 2 years ago
Weirder still, the discounts stack! So blind people can benefit from buying a black-and-white TV for an additional discount.

I've given this a lot of thought in the past. The best I could come up with is that "legally blind" could still allow for someone with _very poor_ (colour) vision...

Comment · 2 years ago
Ehhh. Feel like CAP theorem is a bit overrated. It's correct from a theoretical purist point of view, but you can still solve many of these kinds of issues in practice. (Similarly, people overstate the halting problem - which can be solved for computers with finite memory.)
Comment · 2 years ago
Let's plug my own "joke" website about my love of Bell Bollards: https://bellbollard.com/

We have bell bollard t-shirts: https://www.zazzle.co.uk/be_more_bollard_t_shirt-23500842774...

And we like to take photos pretending to be bell bollards: https://twitter.com/search?q=%23bellbollard

If anyone else wants to get in on this action, you're more than welcome. :D

Comment · 2 years ago
Why would this be easier than just making a diamond?
Comment · 2 years ago
Gutted to hear this.

I used these in London and they were magical and extremely convenient. I would show them to visiting friends as if they were one of London's main tourist attractions!

I knew they relied on some manual labor (bills were delayed), but assumed this was only an intermediate step to collect more real-world training data (until they sorted out the AI).

I still think this is the future though. They could reduce staffing costs and free-up floor space that would otherwise be used for self-checkouts. All the while actually drastically improving the customer experience too.

If someone cracks it, it may make it impossible for other supermarkets to complete economically.

As a fun aside, all the stores were incredibly over-staffed and helpful. If you couldn't install the app they had a browser-based fallback (type "fresh code" into the amazon searchbar on a mobile). They could also lend you a battery bank if you were low on battery. I think they even had phones to lend out to those without smartphones. It was all very optimized around customer experience first and foremost and with no real attempt for the stores to be profitable.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton