I seem to have found a bug (or the word list is drastically different from Wordle). The game says I have 3 possible words remaining, but every Wordle solver website says I only have 2 (and I only have 2 guesses remaining, so this is the difference between the game being winnable and not). The guesses I used for today were WRITE,BOODY,VOUCH,COMMA (and at this point the only two possible words are FOCAL and LOCAL, but it says that there are 3 possible words).
Another point of confusion is that the first row says 2318 possible words, but there only seem to be 2309 words in the dictionary in the code
There are two different Wordle word lists--the set of legal guesses (roughly 13k) and the set of words in the solution list (roughly 2k). The latter list is curated to be a set of fair, interesting words, excluding plurals and more obscure words. Most Wordle solvers use knowledge of what words are in the Wordle solution database to pare down the set of "possible words". But with Don't Wordle, the "legal guess" list ends up being the more interesting one to show "remaining possibilities" for.
https://scoredle.com/ is a site that shows possible remaining words using the larger "legal guess" list, so you can see that you could have also guessed "SOCAS".
> Another point of confusion is that the first row says 2318 possible words, but there only seem to be 2309 words in the dictionary in the code
There were 2318 remaining possible words AFTER your first guess, which eliminated ~11k possibilities.
This may be a spoiler somehow, but one of my guesses was ZONAL, which appears to be valid based on what you’ve guessed so far? That could be the 3rd possible word. I don’t know if it’s in the Wordle list or not.
>The game says I have 3 possible words remaining, but every Wordle solver website says I only have 2
Once you finish the game, if you have any rows with 25 or fewer valid words remaining (shown to the right of the row), the word count becomes clickable. It will open a modal that will show you the valid words remaining after that stage of the game. I went ahead and entered your same sequence of words, and the the other word remaining was SOCAS. That is a valid word in the NYT official Wordle game.
>Another point of confusion is that the first row says 2318 possible words, but there only seem to be 2309 words in the dictionary in the code
There are different word dictionaries in the code.
4 states x 5 letters x 9 guesses is only 180 possible stoplight strings (of green/yellow/gray/black), if I'm doing my math right? So you could just pick 180 emoji and use four of them :)
I thought about this as well, but sadly, last I checked some decently popular apps (Twitter, WhatsApp, some others) don't support emojis in URL paths, only in domain names. So the emoji technique could work for message threads in some apps, but it would look pretty strange in others.
(I've been helping @DungZeekFu a bit with Quordle and am curious for any ideas around this though!)
Well, you need 180 characters, so are there 90 good usable characters, or 60, or 45 that will work?
I’m not suggesting doing a full UTF mapping onto base64, but just 1..180 mod 3 => char base64[3] would give you 182 board positions in three URL characters.
base64 would be pretty neat! I also wonder what non-emoji unicode characters are commonly supported in paths... If say, CJK character sets were supported by most apps, single-character paths would even work.
True, if you are only shooting to solve it in 9 then it can be easy with the right strategy. But many in our friend group are no longer satisfied with 9 and want 7 or fewer guesses :)
It's really cool! one small request: Can you switch the colors for "guessed, not in word" and "not guessed yet" letters on the keyboard? It's opposite from the original and makes it confusing.
I do, which is how I immediately noticed it was there when I went to the site. I'm just not a big fan of the "I've got mine so screw everyone else" mentality and I'm happy to suggest making simple changes that will improve things for others.
One of today’s words appeared recently. I don’t know how many 5-letter words there are, but I feel like the optimal time between appearances should be a bit longer. (Not to mention this word is an alternative spelling, which may be frustrating to some.)
Hey my partner plays a lot of quordle and had the following feedback:
Three things:
1. Love it! Thank you!
2. Could there be a better contrast between keyboard letters and the game board? They’re a bit too similar. I use dark mode, but it seems there is the same lack of definition in light mode as well.
3. Is there any way the whole game could be visible on mobile (e.g. iPhone12 Max) so the last few rows of the game board don’t need to be scrolled?
If you need CSS help or help with the responsive design, let me know! I'd be happy to help. Switched from Wordle after NYT to Quordle and definitely prefer the challenge of Quordle.
My friends and I have been finding Wordle a little too easy lately so I decided to make this cursed version the other day and we have been enjoying the extra challenge. Credit goes to https://zaratustra.itch.io/dordle for inspiring this version. Any feedback is appreciated (especially around the keyboard)!
I have had one way before they shipped out the SDK, and all I have to say is that it is quite a bit more janky than the hype lets it seem.
Fingers will disappear without notice when nothing all that crazy is happening and the frame rate of the device (which is speced at 120+ fps) is much closer to around 45-55 fps. This leads so some major problems with long term finger acquisition that has to be handled by the developer. Quite frustrating to do things yourself that should be handled by the SDK.
While I understand that this SDK batch is a "beta/alpha" test, it is much buggier than it should be. The SDK will hang the entire OS quite often, and there is simply no way to detect if the device is actually plugged in. It will report invalid finger data rather than telling you that no device exists.
And the javascript API is so new, that it is borderline useless. It doesn't even properly report finger width, which is kind of sad since that worked many versions ago.
Overall a cool device with lots of hype, but needs a lot more work to even be mildly useful for anything more than just simple gestures.
It's possible your device has older hardware. I have one from several weeks ago. It does indeed get 120+ fps even with the JavaScript API. Fingers do drop, but I notice that problem less in "precise" mode which is closer to 60 fps.
The JavaScript API doesn't do much for you, but the data is still quite good coming over the WebSocket. I've used it to create some galleries of gestures, and a gesture diagnostic tool. I've been trying to come up with solutions to the problems you've described... if it starts working out I'll release a 3rd-party JavaScript library for better finger permanence and filtering out noisy data.
Updating to this post: I was able to test on newer Leap hardware and fingers no longer drop or jitter. I don't think a JavaScript library will be necessary to filter noise or track fingers in the production version.
You can skip data-binding, the update pattern and SVG for this kind of step-by-step animation. I use Canvas to render these and just a few d3 functions (scales, extents, json). Here's another example to learn from that uses similar techniques to get good performance out of Canvas:
If vim actually supported other keyboard formats properly (rather than making the user redefine them from scratch) I would switch in a heartbeat. But until then, vim is useless to me.
Another point of confusion is that the first row says 2318 possible words, but there only seem to be 2309 words in the dictionary in the code