๐ช๐ช๐ช๐ช๐ชโฌข42โฌข ๐ช๐ช๐ช๐ช๐ชforty-two ๐ช๐ช๐ช๐ช๐ช, ๐ โ๐ค๐.eth - ๐ฆ twitter.com/1350970179128356866
"โฌข๐ช๐ช๐ช๐ชโฌข โฌข๐ช๐ช๐ช๐ชโฌข โฌข๐ช๐ช๐ช๐ชโฌข โฌข๐ช๐ช๐ช๐ชโฌข โฌข๐ช๐ช๐ช๐ชโฌข โฌข๐ช๐ช๐ช๐ชโฌข โฌข๐ช๐ช๐ช๐ชโฌข โฌข๐ช๐ช๐ช๐ชโฌข โฌข๐ช๐ช๐ช๐ชโฌข โฌข๐ช๐ช๐ช๐ชโฌข โฌข๐ช๐ช๐ช๐ชโฌข โฌข๐ช๐ช๐ช๐ชโฌข โฌข๐ช๐ช๐ช๐ชโฌข โฌข๐ช๐ช๐ช๐ชโฌข"
Polyglotism: 2 (wordle_en, wordle_it)
#Tweets: 6
Last Tweet: ๐ฌ๐ง ๐2 for 236 RT @1kisfud: Wordle 236 2/6*.. (about 4 years)
Average Tweet score: ๐ฆ 3.5 / Average moves of the internet: 4.11
| WordleTweet by Score
Loading...
| Average score by language
Loading...
|
| Score by incremental day.. [I wish i had recorded the twit date - only DB creation date]
I count failures (X) as eights (could be 7,8,9,10... lets arbitrarily say 8 #aitdc)
Loading...
| |
Interesting enoguh, I sorted them by creation date but it doesnt still seem to be in order. Funny! found the problem: I could use `twitter_created_at` but i have a lot of nil for my first days naive implementation. I can just probably deprecate them soon-ish and then its all clean. Idea: use the Google Chart table and populate it - this way you can sort it client-side and noone can complain. Plus you get a number of interesting sort-by ;)
+
2022-02-10
๐ฌ๐ง ๐2 for 236 RT @1kisfud: Wordle 236 2/6*.. (about 4 years ago)
+
2022-02-09
๐ฎ๐น ๐3 for #235 @1kisfud @nullpackets @JohNo.. (about 4 years ago)
+
2022-02-09
๐ฌ๐ง ๐5 for 235 RT @nullpackets: @misfortuna.. (about 4 years ago)
+
2022-02-09
๐ฎ๐น ๐3 for #235 RT @Obit7777777: @1kisfud @n.. (about 4 years ago)
+
2022-02-09
๐ฌ๐ง ๐3 for 235 RT @1kisfud: Wordle 235 3/6 .. (about 4 years ago)
+
2022-02-09
๐ฌ๐ง ๐5 for 235 RT @misfortunateApe: @1kisfu.. (about 4 years ago)