94 karma · joined December 17, 2017
That's what the article is about. It's a policy change.
I certainly won't defend Apple and Google's app store monopolies and control. However, Kotlin was actually a case of Google listening to the developer community. Google could have, and wanted to, push Dart (see Flutter) on Android. But the Android development community was already adopting JetBrain's Kotlin. Google listened and embraced Kotlin instead of pushing their own thing. It was not a hostile act.
4th result is HN for me https://www.google.com/search?q=%22code+that+protects+users+...
Obviously something changed as the emails just started going out recently. Maybe it was a recent code change introducing a bug on their end, that's fine software has bugs, but they could explain it. Maybe attackers are doing something different, which is triggering an old bug causing incorrect emails. Or maybe LastPass still doesn't really know and is just giving a potential reason, like they did earlier saying it was credential stuffing.
I'd already stopped using LastPass years ago and deleted my account when this current mess started, so they weren't really going to win me back anyway. But the (current) response to this incident leaves plenty of unanswered questions.
I haven't used LastPass since, at the latest, 2017. I had actually deleted all my passwords from my LastPass vault, but originally kept the account because of LastPass's password sharing feature, though I stopped using that as well. I believe I had the LastPass extension installed on both Chrome and Firefox, on both Mac and Ubuntu. I primarily used Chrome on Mac. I did have uBlock Origin on those setups as well, but I really doubt that's the vector, it's likely just incredibly popular with all users of Hacker News. My LastPass password was globally unique and between 15 and 20 characters long (with some symbols and digits). This password shows no matches at https://haveibeenpwned.com/Passwords . I considered sharing the password here, but just in case an old version of my vault is out there somewhere somehow I'm not going to. My understanding is that such a password would be so incredibly impractical to brute force that it's not worth considering. Unless I'm outdated/wrong on that, that means the password leaked in clear text (or hashed with a broken hashing method). As I haven't typed that password since at least 2017 and I can't imagine LastPass is storing passwords in clear text, I'm inclined to believe the password was stolen in clear text from client machines (either LastPass extension exploit or malware) in or before 2017. It's weird they were not used earlier, but as LastPass doesn't allow new IPs by default, maybe the attackers knew this and were sitting hoping an additional exploit would allow their user. But now they're just trying in the off chance someone clicks the "That's me" link in the email. This doesn't explain the more recent claims, personally I'm inclined to disregard them as unrelated noise (user confusion, reused password, etc).
Time Monday, December 27, 2021 at 3:05 PM EST Location São Paulo, SP 01323, BRAZIL IP address 160.116.190.69
I haven't used LastPass since 2016 or 2017.
"when an employee resigns as a result of the employer creating a hostile work environment. Since the resignation was not truly voluntary, it is, in effect, a termination. For example, when an employer places extraordinary and unreasonable work demands on an employee to obtain their resignation, this can constitute a constructive dismissal."
Similarly, "gluten-free" is associated with breads, pastas, etc. Not rice or other non-imitation products.
The Perl library was `Net::AIM::TOC` and later `Net::OSCAR`
Honeycomb, Android 3.0, was released Feb 2011 for tablets. It was a radical new UI and introduced several new APIs. It was the largest Android update ever, except that no devices were updated to it. Android tablets didn't sell very well and developers had little to no reason to support Honeycomb.
Ice Cream Sandwich, Android 4.0, October 2011. This refined the Honeycomb changes and was appropriate for use on phones. It did work on tablets but wasn't really optimized for them until 4.1/jellybean.
Honeycomb wasn't a fork or anything, but the strong divergence and poor sales of Android tablets meant that no one wanted to target Honeycomb until they were actually targeting Ice Cream Sandwich, and then at that point it was barely worth supporting Honeycomb tablets, but still work supporting Gingerbread phones.
I don't think it's particular relevant to the iPadOS situation.
And bitwise operations https://discuss.kotlinlang.org/t/when-does-bit-fiddling-come...
And maybe handling generics. I haven't had any issues, but kotlin is a bit stricter which is generally a good thing, but I'd believe that for some edge case it makes things harder.
Like coconuts
For example "distance to mars" says 54.6 million km, which is the theoretical minimum. "distance to venus" says 261 million km which is maximum. I believe it was Jupiter that previously gave an average distance but now I'm seeing minimum.