I just think they got distracted when the problems got harder, and instead of tackling them head-on, they now waste a lot of their resources on busywork - good intentions notwithstanding. Sure, it’s more fun standardizing sparkling disco balls than dealing with real-world pain points. That OpenType is a good and powerful standard which masks some of Unicode’s shortcomings doesn’t really help.
It’s not too late, and I hope they will find their way back to their original mission and be braver in solving long-standing issues.
Actual news: A group was in risk of being considered left wing extremist, which could jeopardize their non profit status. The court ruled in their favor actually.
It just so happens that the wording of the court’s justification of the ruling irked some people - quickly paraphrasing, “Marx teachings might be contrary to democracy but this people aren’t acting on those teachings so their reading isn’t reason to consider them extremists”.
Some groups are worried that this wording about marx sets a precedent, being unclear if there is actual legal concerns.
For the first case, sending a hash would prevent the server from learning a password that is not in the dictionary, something like password5 would hash to gibberish.
For the second, the server needs to know what to actually send back. I believe Google's malicious website check works (or used to) by truncating a hash an then just sending the answer for some 128 or so websites and have the browser figure out which of them the user wanted to visit. That creates some deniability over witch website you actually visited and should be also usable to prevent the server from learnering what you actually looked up.
So yes, I think you could design a more secure Protokoll. Though general security disclaimer the people trying to read your letters probably spend more time attacking than I spend writing this post.