Hacker News Reader

I would argue it’s actually easier to serve content to logged out users as you can cache the whole response and serve it at the edge. Then it “just” becomes a cache expiration problem.

View on HN

I have seen right here on HN where my request cannot be processed, but it loads fine in a private browser window.

Logged in users receive more errors.

Thanks, caching, for allowing me to continue procrastinating.

Correct, we push static assets to the edge. However not all SASS products are the same, there is a spectrum of features that can be pushed to the edge and some cannot. The engineering comes from cost, usability, reliability, etc...

Ultimately we prioritize our logged-in customers.

Reply on news.ycombinator.com