Wow, they're actively removing data off the app on your phone? Good reason to never use MS authenticator for anything important. This is also assuming that they're never wrong about this, and that it is foolproof with no false positives.
It seems that there's a big difference between "not supported" and actively removing account/auth data from someones phone. This has made me reconsider my 2fa providers. I might have to look at some sort of hosted option that doesn't have this issue. I wonder what the policies are for this kind of thing with authy and okta (and other major 2fa auth platforms).
I mostly agree with you, but if a human straight up copies work under copyright they’re violating the law. Seems like a LLM should be held to the same standard unless they should be even less beholden to the law than people.
It’s also incredibly hard to tell if a LLM copied something since you can’t ask it in court and it probably can’t even tell you if it did.
I don't have much of an opinion on React as a library, although they do use it for our web frontend at my work. However something I noticed in the past when I was doing some web dev work out of AUS was that some websites would have incredibly buggy behavior. Keep in mind this was around 10 years ago so some things might have changed. After doing some debugging it turned out that some of the libraries were fairly large, and they didn't have co-located CDN's in the area. The specific ones in that were jQuery. That caused some of the JS libraries to not fully download, or just some of them to time out.
That's a mostly fixable problem with having something like a pipeline that minifies the libraries and has them being downloaded from somewhere closer to your users, or putting them on a better CDN, but a lot of people don't have the time/option/money to do that. It was pretty obvious in that instance since a lot of that was wordpress development at the time and things like plugins/extensions usually don't bother. When I was doing similar development in the US I never saw any of that kind of behavior since so many libraries at the time were hosted on the West Coast where I lived. Also most developers I know aren't super resource limited on their hardware (desktop/laptop or mobile), which might be a factor.
I'm not sure if this is what people are referring to, but just something to consider.
I was an early user of insync (Linux and google seive) and had issues with it when they added one drive support. I tried it out when I was getting all of my stuff off of google a while back. I pay for office and one drive so if I could consolidate it would be nice.
It seems that there's a big difference between "not supported" and actively removing account/auth data from someones phone. This has made me reconsider my 2fa providers. I might have to look at some sort of hosted option that doesn't have this issue. I wonder what the policies are for this kind of thing with authy and okta (and other major 2fa auth platforms).