Guess the daily Wordle in one try using the tweet distribution
21–30 of 122 posts
Re: Guess the daily Wordle in one try using the tweet distribution
#22What are the "⬛ squares taking social media by storm"?
Re: Guess the daily Wordle in one try using the tweet distribution
#23Re: Guess the daily Wordle in one try using the tweet distribution
#24What are the "⬛ squares taking social media by storm"?
Re: Guess the daily Wordle in one try using the tweet distribution
#25Re: Guess the daily Wordle in one try using the tweet distribution
#26Re: Guess the daily Wordle in one try using the tweet distribution
#27My favourite part of this is accounting for some fake grids. Kudos! I have been so curious lately as to whether this was possible. EDIT: The next question is which (if any) of these signals can be removed and still get it in 1 guess. Or if there are any other signals. Or how many tweets are needed (is 50 enough? 10? or 1000? 10k?)
(Edit: drat, HN filters out the Unicode colored-block characters).
Re: Guess the daily Wordle in one try using the tweet distribution
#28Earlier quoted context omitted.
Huh, I thought HN stripped out emojis from posts. Has that changed, or is there a limited subset that are available?
Maybe because ■ is part if ASCII? Edit: ⬛⬜ work, the colored ones don't.
Re: Guess the daily Wordle in one try using the tweet distribution
#29My metagame is guessing my friend's guesses.
Re: Guess the daily Wordle in one try using the tweet distribution
#30My favourite part of this is accounting for some fake grids. Kudos! I have been so curious lately as to whether this was possible. EDIT: The next question is which (if any) of these signals can be removed and still get it in 1 guess. Or if there are any other signals. Or how many tweets are needed (is 50 enough? 10? or 1000? 10k?)
The simulated distributions it's comparing to are based on 1000 runs per 5-letter word.
Anecdotally, 250 was enough to get it working for those simulated distributions, 100 and below it became increasingly noisier. A higher N would be nice, but I didn't spend more time optimizing the performance for the simulation code beyond what was needed to get this working.