Yeah ran into that a month or so back with some service or other. Account was locked out, I told the prompt I was looking for an account unlock, I got to listen to “you can do most things by logging into your account at” for 45 minutes.
I definitely wouldn’t call “local llm features” dangerous.
Edit: I suppose the tab grouping may not be local? Their docs don’t really specify one way or another. So I could be wrong in that one. The rest is definitely local, minus the “you have to sign in with an llm account” sidebar chat thing.
You call it an invasion of privacy, I call it fucking with friends while teaching them to be cognizant of who is watching what they do. You realize they can (and did) just immediately change their password right?
I’m also not sure how “the average person treats their passcodes and passwords like everyone is intentionally looking away” somehow strengthens “lock making the phone less secure behind a passcode” as an argument.
And yes, it 100% lowers the security of the phone. Which absolutely is your choice. Which I also do, and have done with my wife and kids phones. But the idea that a passcode is somehow a solution is just silly.
Not as silly as a 24 hour wait controlled by google, but still silly.
I agree a day wait is bullshit, but you think a passcode is enough to keep someone from… anything? You can shoulder surf a passcode in no time at all. Hell, it’s not even difficult. Go to a bar, talk someone up, give a legit reason to use someone’s phone, intentionally lock and force a passcode and 99% of people at bars will put their pin in within eyesight, or tell you the code.
A passcode isn’t as big a deterrent as most people seem to think it is. It’ll keep you out of an unattended phone you found, but there are plenty of ways to socially engineer your way into having it for the vast majority of targets.
And yes, you likely wouldn’t give your passcode out. But this is how a number of ne’er-do-wells got unfettered access to hundreds of iPhones, and prompted Apple to put a semi similar 24 hour lock on certain security actions if you aren’t in a “known to the phone” location (somewhere you frequent like home or work).
Edit to note: passwords aren’t much better. One of my hobbies in college was shoulder surfing classmates passwords just to repeat it back to them later in the day. Though on a phone you have far fewer reasons to type in an associated accounts password.
Well, yes. In so far as they’ve added a new opt in button, and it would be silly to assume every user wants it off now. Instead, users that previously installed get a “turn off AI here” button when the update happens.
That’s just the norm tbh. You learn new techniques, the language gets new optimizations, keywords and shortcuts. That doesn’t mean your code is unmaintainable.
It really depends on the situation. Can I write maintainable code? Yes, to the extent that the average senior dev can.
But that isn’t the same as being afforded the chance to write maintainable code. I’ve been part of teams where the timeline is so tight that technical debt is just a thing that builds up to be dealt with “later” and more stress is put on getting things done instead of keeping things maintainable.
The fact of the matter is that humans can while LLMs currently can’t.
On top of that, a human dev is going to be able to understand context a hell of a lot easier if they’ve previously worked on it, even if the code is less maintainable.
Soon to be added to applications:
“Please check this box stating that you are aware AI will be used for the assessment. Failure to check this box will result in a denial.”
Yeah ran into that a month or so back with some service or other. Account was locked out, I told the prompt I was looking for an account unlock, I got to listen to “you can do most things by logging into your account at” for 45 minutes.