ๆตฆๅณถใฎไบ, ๐ ๅๅฝใฎ้ ใฃใ - ๐ฆ twitter.com/192623930
"ใกใญใทใณใฎ้ ใฃใๅจไฝใๅ็ฉใกใคใณใ็ฌ่ซ้กๅคใใ็ก่จใใฉใญใผใๅฎน่ตฆใไบบ้ใจใใฆๅคฑ็คผใงใชใ็ฏๅฒใชใใ็ดฐใใไฝๆณใซใฏใใ ใใใพใใใ"
Polyglotism: 2 (wordle_at, wordle_en)
#Tweets: 2
Last Tweet: ๐ฌ๐ง ๐3 for #591 Wordle 591 3/6 โฌโฌโฌโฌ๐จ ๐จโฌ๐จโฌโฌ ๐ฉ.. (over 2 years)
Average Tweet score: ๐ฆ 3.0 / Average moves of the internet: 3.79
| WordleTweet by Score | Average score by language |
| 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) | |
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 ;)
+
2023-01-31
๐ฌ๐ง ๐3 for #591 Wordle 591 3/6 โฌโฌโฌโฌ๐จ ๐จโฌ๐จโฌโฌ ๐ฉ.. (over 2 years ago)
+
2022-04-11
๐ฆ๐น ๐3 for #296 Wรถrdl 296 3/6 ๐ฉโฌโฌโฌ๐จ ๐ฉโฌ๐ฉ๐ฉ๐ฉ ๐ฉ.. (about 3 years ago)