> We found that some web customers were unable to access the puzzle, and found the cause of the problem to be App Engine’s limit on the size of outbound request headers (16KB). Users with a large amount of third-party cookies had their identity stripped from the proxied request. We made a quick fix to proxy only the headers and cookies we needed and we were back in action.<p>That’s pretty funny. Users of NYT are sending request headers with <i>sixteen kilobytes</i> of tracking data. Maybe that’s the real problem eh?<p>I wonder which news website has the largest amount of trackers. If I let the CNN home page sit open in chrome, I can come back an hour later and find <i>thousands</i> of requests blocked by uBlock.
Doesn't this lead to vendor lock-in? All these Google proprietary services seem like they would be a big issue if they decide for whatever reason to migrate away from GCP.
If anyone wants to try collaborating on crosswords in real-time, try<p><a href="https://squares.io/" rel="nofollow">https://squares.io/</a><p>You can upload .puz files or let it download from NYT with your subscription, then share the link with friends.<p>(Web only for now, sorry.)
Since there are people from NYT here, can you point me in a direction to help figure out why my streaks have been all messed up the past few months? Not sure if it's an app bug or something on the backend, but puzzles are retroactively being marked as being completed perfectly when they're not. Email in bio if you'd like to discuss more.