I once had to solve a captcha in a foreign language because of that. Wasn't something obvious like motorcycles either, it was something like "click on all hamsters" in a grid full of various rodents.
I suppose the point is that it's not the voiceless glottal fricative?
To my ears [ħ] sounds closer to [x] and [χ] than to [h] (even though the place of articulation is closer to [h]), but I'm sure it's different for people who (natively) speak a language with all three.
Yeah, I imagine it's an interesting question which of these sounds is more perceptually similar to the target sound. It may well depend to some extent on the native language(s) of the person who is listening.
My team uses Matrix and I must say I'm not satisfied. There are messages that I get a notification for every time I open the app, and "mark as read" buttons that do nothing, especially if you use threads. This is something that has supposedly been fixed many times, but it's one of these persistent issues that keep coming back.
Also, as far as I can tell, there is no real diversity in clients even though Matrix is in principle an open protocol. Everything is either Element or a fork of it, or at least is built on matrix-react-sdk, which makes them all effectively the same.
Something isn’t right here; thread notif problems should have been solved a year or so ago.
And most apps are not element forks - eg FluffyChat, Nheko, Cinny are all great fully featured apps and separate codebases. The only Element fork i can think of is SchildiChat. Meanwhile matrix-react-sdk doesn’t even exist any more.
> FluffyChat, Nheko, Cinny are all great fully featured apps and separate codebases
Ok, I was mistaken about everything being an Element fork.
To move the goalposts slightly though --- do any of these apps properly support threads (i.e. messages in threads show up in and only in separate views)?
Afaik Element Web (and the legacy Element mobile apps) are the only ones which have done threads so far, perhaps because the notif problems you mentioned put off the others. These have been fixed now, but others (even Element X) have yet to catch up.
Correct notifications are essential for a messaging app/service.
If people hit those bugs, I hope some of them have the time to speak up in the Matrix channel for that app/platform or find/create/bump the Github issue for it. While Matrix needs continued love, its ecosystem seems like a great protocol & app to keep supporting with feedback.
Messaging apps are hard to get all perfect (even some major ones, not naming names), and what Matrix accomplishes is pretty impressive; I hope Matrix & Element will continue to mature. (For hope, the first iPhone was pretty limited and easy to dis, but look at it now.)
Parenting still needs to happen, especially if your 17-year old child is autistic as was the case in this article - they do not have the maturity of a typical 17-year old.
I'm not saying you're wrong, but I wonder if this "missing piece of insight" is at least sometimes an illusion, as in the "monads are like burritos" fallacy [0]. Of course this does not apply if there really is just a missing fact that too many explanations glossed over.
Verified pre and post conditions would be nice. Especially in the era of LLM's, which can usually fill in the implementation given a sufficiently clear specification.
In fact, Facebook is so sure they already have everyone that new users are often flagged as suspicious and banned by their automated tools without even doing anything. No other site could afford to do that.
Worse than that. I have a Facebook account that is at least 16 years old (yes, from the very first years of Facebook's existence) that I log in a few times a year when I have to use Facebook to do something. I don't post or read anybody's post -- a few years ago I unfollowed everybody (but still remain connected), just like what this article says. I might have actually used this tool but I am not sure. Guess what, my 2-factor auth enabled account got disabled for absolutely no reason. Same login location, same browser. I had to do a stupid video verification to reenable the account, something I refused to do for opening an Instagram account.
This won't work if implemented browser-wide as malicious website will just adjust the URLs for their images to compensate. In general, URL file extension snooping only causes more problems than it solves.
Maybe. It seems sensible to me that if the UA is requesting a path that ends in .jpg (for instance), they're expecting a JPEG and the UA should accept image/jpeg. At least if this escalates the arms race, user-hostile websites won't commit this specific crime, instead they'll serve content that better matches the URL.
