๐Ÿญ produ   ๐Ÿ  Home | ๐Ÿ“Š Stats | ๐Ÿ‘ค Users | ๐ŸŸฉ Wordle Tweets | ๐Ÿ“ WGames | ๐ŸŒ Dialects

User @PoCousKe

ใƒใ‚ณ, ๐Ÿ“ Tokyo-to, Japan - ๐Ÿฆ twitter.com/1127096094695911424

"ใƒใ‚ณใกใ‚“ใฃใฆๅ‘ผใ‚“ใงใญ๏ผ่จ€่ชžใ‚„่‡ช็„ถ็ง‘ๅญฆใŒๅฅฝใใชSE ใƒใ‚คใฎ่…็”ทๅญ ๆฅไธ–ใฏ็Œซใซใชใ‚ŠใŸใ„ ใ‚ฒใƒผใƒ : ๆ”พใ‚ตใƒขใ€LiveAHero"

Wordle stuff

Polyglotism: 3 (wordle_it, wordle_es, nerdlegame)

#Tweets: 6

Last Tweet: ๐Ÿ”ข ๐Ÿ†3 for #66 nerdlegame 66 3/6 โฌ›๐ŸŸช๐ŸŸชโฌ›โฌ›๐ŸŸฉ๐ŸŸชโฌ› .. (about 3 years)

Average Tweet score: ๐Ÿฆ 4.5 / 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)

๐Ÿฆ 6 Tweets Detail

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-03-26 ๐Ÿ”ข ๐Ÿ†3 for #66 nerdlegame 66 3/6 โฌ›๐ŸŸช๐ŸŸชโฌ›โฌ›๐ŸŸฉ๐ŸŸชโฌ› .. (about 3 years ago)
+ 2022-02-26 ๐Ÿ‡ช๐Ÿ‡ธ ๐Ÿ†6 for #253 Wordle (ES) 253 6/6 โฌ›โฌ›๐ŸŸจ๐ŸŸจ๐ŸŸจ โฌ›.. (about 3 years ago)
+ 2022-02-26 ๐Ÿ‡ฎ๐Ÿ‡น ๐Ÿ†4 for #253 Wordle (IT) 253 4/6 โฌ›โฌ›โฌ›โฌ›๐ŸŸจ โฌ›.. (about 3 years ago)
+ 2022-02-26 ๐Ÿ‡ช๐Ÿ‡ธ ๐Ÿ†5 for #252 Wordle (ES) 252 5/6 โฌ›โฌ›โฌ›๐ŸŸฉ๐ŸŸฉ โฌ›.. (about 3 years ago)
+ 2022-02-26 ๐Ÿ‡ฎ๐Ÿ‡น ๐Ÿ†6 for #252 Wordle (IT) 252 6/6 ๐ŸŸจ๐ŸŸจโฌ›โฌ›โฌ› โฌ›.. (about 3 years ago)
+ 2022-02-24 ๐Ÿ‡ฎ๐Ÿ‡น ๐Ÿ†3 for #250 Wordle (IT) 250 3/6 โฌ›โฌ›๐ŸŸฉโฌ›โฌ› โฌ›.. (about 3 years ago)

| Back to twitter users