zlacker

[parent] [thread] 3 comments
1. mlrtim+(OP)[view] [source] 2023-11-27 12:20:49
Additionally the infrastrucutre is not free either. Even without ads (which is fine by me), serving up the full suite of tools to logged out users is very expensive and much harder to control

At our company we're trying to do the same thing now, supporting logged out users is just too expensive and not worth it.

replies(1): >>zeitg3+08
2. zeitg3+08[view] [source] 2023-11-27 13:17:13
>>mlrtim+(OP)
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.
replies(2): >>double+Z8 >>mlrtim+kz
◧◩
3. double+Z8[view] [source] [discussion] 2023-11-27 13:24:12
>>zeitg3+08
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.

◧◩
4. mlrtim+kz[view] [source] [discussion] 2023-11-27 15:46:08
>>zeitg3+08
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.

[go to top]