Thank you. I don't think I was the only one that had reached Wordle fatigue.
Hoping not to overgeneralize, but it's a bit sad seeing so many bright minds engaged in dissecting and remixing something so plain, just because it's another hype wave for which we can all apply the specific problem solving skills we know.
The only change I'd perhaps recommend would be not hiding this thread itself.
I don't find it sad at all. I find it fun and enjoyable that people have seen the power of a good simple fun game and that it wasn't hard to make something good and even better it still required more thinking about the gameplay than the implementation.
Many lessons to be learned here for any hacker, imo.
It is a shame. It's a game that's trivially optimisable but requires you to avoid doing so to have fun. It's a game that already existed, so must have become popular for another reason: because they came up for a way for people to brag about their intelligence in a socially acceptable way.
Ironically, it's disappointing to see how poor the vocabulary of some English-first-language speakers is & how readily they blame the game for using quite common words that they don't know.
Several years ago, I was sick of hitting pay/signup walls for sites I already knew I was never going to join but kept clicking because I either didn't know where the link was going or I just forgot that site was walled off. I made an FF add-on that applies a specified style to any elements with attributes matching a given regular expression. It can do text content matching too but, as it's currently programmed, it tends to apply to an element too far up the tree.
It was intended for personal use but, if anyone is interested, it's a public github repo and, because Mozilla requires an add-on to be registered to be usable in any practical sense, it is up on the add-on site. There's no proper UI, the only interface is through preferences and it's just a textarea where the JSON config goes (example given below the textarea).
Do you happen to know how you would you implement something like this, but have it read in a list of banned words/domains, rather than just having one hard-wired keyword?
I've long wanted something like Google Hit Hider by Domain[0], but for HN, so I can block some of the crap that gets posted here. I've managed to knock together something really clunky in Go that sort of does what I want but needs me to run it as a CLI app. Id love to have the convenience of a Grease/Tamper-monkey script that does this, but JS is not my strong point, so I wouldn't know where to start.
I guess there are lots of things that consume RSS, but you might see if you can add filtering there.
For example I wrote a rss2email application, and I added the ability to ignore entries based on regexp-matching against their titles, or bodies. I imagine many RSS projects have similar facilities, and if not would welcome contributes to add such a thing.
Hoping not to overgeneralize, but it's a bit sad seeing so many bright minds engaged in dissecting and remixing something so plain, just because it's another hype wave for which we can all apply the specific problem solving skills we know.
The only change I'd perhaps recommend would be not hiding this thread itself.