ฮนzฯ ะผฮนะผฮฑััฮฑ๐ฏ๐ต๐ฎ๐น, ๐ Massa, Tuscany - ๐ฆ twitter.com/124411594
"Tweet in giapponese dell'insegnante di giapponese. ใคใฟใชใขใงๆฅๆฌ่ชๆๅฎคใ้ๅถใๆฅๆฌ่ชใ้ใใฆๆฅๆฌใ็ฅใฃใฆใใใใใใๆฅฝใใ้ทใๆฅๆฌ่ชใๅญฆใใงใใใใใใๅบๆฌใชใณใฉใคใณๆๆฅญ(https://t.co/ALWlzzp9jm)ใhttps://t.co/yCvWQKedbs"
Polyglotism: 2 (wordle_it, wordle_en)
#Tweets: 3
Last Tweet: ๐ฎ๐น ๐3 for #381 Par๐ฎ๐นle 381 3/6 ๐จโฌโฌโฌ๐ฉ โฌ๐ฉ๐ฉโฌโฌ.. (about 3 years)
Average Tweet score: ๐ฆ 16.3333333333333333 / 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 ;)
+
2022-02-17
๐ฎ๐น ๐3 for #381 Par๐ฎ๐นle 381 3/6 ๐จโฌโฌโฌ๐ฉ โฌ๐ฉ๐ฉโฌโฌ.. (about 3 years ago)
+
2022-02-16
๐ฌ๐ง ๐4 for #242 Wordle 242 4/6 โฌโฌ๐จ๐จ๐จ โฌโฌโฌ๐จโฌ .. (about 3 years ago)
+
2022-02-16
๐ฎ๐น ๐X for #380 Par๐ฎ๐นle 380 X/6 โฌโฌโฌโฌโฌ ๐ฉ๐จโฌโฌ๐จ.. (about 3 years ago)