So the fun word game stops working while commuting by train because it needs to stop me "cheating" in a purely fun /social game by phoning home during the time I have to play it, where the connection is spotty at best, and the quick game loop of guess, read result, think gets janked because of railway cuttings and tunnels?
All because someone coukd read the source to cheat and wouldn't, idk, just copy paste the squares about in their tweets?
Exactly. It's somewhat baffling to me how some people focus so much on the technology aspects of something to the point of forgetting that its success is due to the things that it does not do.
For context, a Twitter bot was recently banned for automatically replying to Wordle tweets and spoiling the next day's word. Preventing that would improve the gameplay experience by defending against malicious disruption.
Not really. The bot can get its data from when NZ hits midnight, hours and hours before America and Europe etc. Even if it was always released at the exact same time globally, nothing to stop a bot solving it / fetching it immediately and replying to users posts from yesterday about what todays one is.
I don't see a point of this. I could probably find the correct word for today by Googling so server/client side does not make any difference if we all share the same word for the day which is I think the major feature behind the success.
The original creator was not able to do that due to infrastructure limitations, but surely NYT would have the proper setup to handle that.