ann@ใใใฐใใชใ, ๐ ไธญใคๅฝใฎๆฅใฎๆฌใฎ็ธๆจกใฎๅฝ - ๐ฆ twitter.com/125986688
"ๆฑๆนใจใใฎ็ตตใๆใใใ่จ่ใซใคใใฆ่ฉฑใใใ่ฉฑใใชใใฃใใใใๆใใใใใใใใชใใจๆใใใhttps://t.co/jaqHWEn75t"
Polyglotism: 2 (wordle_at, wordle_en)
#Tweets: 9
Last Tweet: ๐ฌ๐ง ๐5 for #747 Wordle 747 5/6 ๐ฅ2 โฌ๐จโฌโฌ๐จ ๐ฉโฌโฌ.. (almost 2 years)
Average Tweet score: ๐ฆ 4.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 ;)
+
2023-07-05
๐ฌ๐ง ๐5 for #747 Wordle 747 5/6 ๐ฅ2 โฌ๐จโฌโฌ๐จ ๐ฉโฌโฌ.. (almost 2 years ago)
+
2023-03-31
๐ฌ๐ง ๐2 for #651 Wordle 651 2/6 ๐ฅ10 โฌโฌ๐จโฌโฌ ๐ฉ๐ฉ.. (about 2 years ago)
+
2023-03-25
๐ฌ๐ง ๐4 for #645 Wordle 645 4/6 ๐ฅ4 โฌโฌ๐จโฌ๐จ ๐จ๐จโฌ.. (about 2 years ago)
+
2023-03-13
๐ฌ๐ง ๐3 for #633 Wordle 633 3/6 ๐ฅ1 โฌ๐จ๐จโฌ๐จ โฌ๐ฉ๐ฉ.. (about 2 years ago)
+
2023-02-28
๐ฌ๐ง ๐4 for #620 Wordle 620 4/6 ๐ฅ8 โฌ๐จโฌโฌโฌ โฌโฌ๐ฉ.. (about 2 years ago)
+
2023-02-03
๐ฌ๐ง ๐5 for #595 Wordle 595 5/6 ๐ฅ6 โฌ๐ฉ๐ฉโฌ๐จ โฌ๐ฉ๐ฉ.. (over 2 years ago)
+
2023-01-31
๐ฌ๐ง ๐6 for #592 Wordle 592 6/6 ๐ฅ3 โฌโฌโฌ๐จโฌ ๐จ๐จ๐จ.. (over 2 years ago)
+
2022-06-06
๐ฆ๐น ๐6 for #353 Wรถrdl 353 6/6 ๐ฅ7 โฌโฌ๐จโฌโฌ โฌ๐ฉโฌ๐ฉ.. (almost 3 years ago)
+
2022-05-13
๐ฆ๐น ๐4 for #329 Wรถrdl 329 4/6 ๐ฅ1 โฌ๐จ๐ฉโฌ๐จ โฌ๐ฉ๐ฉโฌ.. (about 3 years ago)