Post should've been titled "1.3 billion passwords were exposed", because, even though the number is slightly smaller, it actually represents something much more important.
If you'd like to change that, you can go to System Settings → Battery → Options → Wake for Network Access
Or just search for "Power Nap" (what it used to be called). They usually wake up intermittently for Time Machine backups, wake-on-lane and other stuff.
I have mine set to `NEVER` [wake for network access] and yet it still makes DNS requests often while asleep.
Curiously, it is able to maintain network connection even through the 1/4" steel of the safe it's stored within. The older Intel MBP doesn't and cannot.
Hah, sounds like OS X! I have every possible Universal Control setting turned off, yet the process continues running and slurping up CPU cycles. It's impossible to kill or really disable unless you turn off SIP, and I'd prefer not to do that.
We want to make you aware of a recent phishing attempt that may have affected you.
An attacker recently submitted fake support requests to our Help Center using email addresses obtained from external sources (such as scraped public data or compromised email lists). As a result, you may have received an unexpected email from our support system, which could appear to be from a legitimate source (such as Discord in this case) and may contain suspicious links.
If you received such an email, we strongly advise you not to click any links and to delete the message immediately.
Please rest assured:
- Your account with us has not been compromised
- No unauthorized access was gained to our systems or customer data
We’re actively monitoring the situation and taking steps to prevent further abuse.
I’m not sure, most of the people I know who like true crime/murder porn are not exactly “morose”. (But I do find their interest unsettling.)
When I was a kid, some teens who were into darker themes (not all but definitely some) had a phase where they were interested in serial killers. It always struck me more as shallow “edgy teen” posturing than anything else. After Columbine this demographic moved on to other interests, as even a performative interest in real-world violence could lead to official harassment.
> It always struck me more as shallow “edgy teen” posturing than anything else
Comment OP here: it was exactly this; the safest, most boring possible way to be transgressive. I didn't talk about it as much as other kids who were like this, so I didn't have to stop once people started to actually care/respond, but I did go from keeping my Harold Schechter books on my bookshelf to in a special box in my closet. Merely knowing about these things gave me a little secret thrill like I was some sort of badass with extreme psychic warding able to go into some secret space that most people couldn't stand. In reality I was just desensitized cuz abusive mom and I'm really glad I grew out of it before I got to the part some kids get to where learning isn't enough and they start experimenting.
This is cool! Might be less of a problem on MacOS, but I'd love a script that automatically turned off sending analytics to Apple every time I do a beta OS update.
Is sending analytics not most of the reason to opt in to beta updates?
I can't think of any upside to installing a release that's likely to have bugs or regressions if you're not going to send the analytics required to find the bugs that impact your software.
I agree! You have to also remember that, if you're the person pushing for something to be priority, it's your job to make it make sense to whoever is responsible for prioritization.
The easiest way to do that is to speak the same language everyone else is. Your product manager probably speaks in dollars (or euros, renminbi, etc). If you provide a good-faith estimate (ballpark ranges are totally fine) that increased test coverage or whatever your technical objective is will cost 200 dev hours, and save 400 dev hours on an annual basis, or reduce the rate of support tickets by 15%, or allow for X future business scenario to be supported or whatever, you'll generally have way better luck. My favorite "trick" is taking tech debt work, and framing it in a way so, not only do I not have to push for it as "tech work", but my PM will actually put it on the roadmap proactively because it just makes sense from a business perspective.
It also gets easier over time. You might get some skepticism at first, but if you have a history of delivering accurate estimates and results over months or years, you'll build trust with stakeholders such that what might've taken a round of meetings to convince them before, can now be a 10-minute conversation.
Sure except that "saving money" is not what makes a company win, and so it's rightly not what makes a career. If you can show that building that new library for $X will streamline engineering by Y% which will allow doubling sales by launching 3 new products - NOW you have a good proposition. (Your "X future business scenario").
Saving money on the current product is only useful if the company has no clue where to go next. Since normally the current product will be gone in 2 years. It can be useful when your company is in long steady production, like a refinery where saving 0.5% would be huge.
This is something people often miss about dodgy code bases. Or about writing a large application in a weird choice for a language. IF you were able to deliver that application AND it's still profitable 5 years later, THEN already it was hugely successful. You can argue that it was not in the correct language and you are wrong because it was ALREADY hugely successful. Same for cleaning up the documentation.
I don't disagree, but I'm not sure if you meant to reply to my comment? I didn't make any references to saving money; the point I'm making is that spending 10 hours this week in order to have 10 additional hours of capacity (ability to build out new features tied to revenue) every month is often a bargain that makes sense.
In the context of full-time engineers, "saving time" actually means that time will be reinvested into product feature development, rather than resulting in less spending on engineering pay. Similarly, engineers spending less time on support, means they can spend more time on feature development.
And I argue that this is rarely the right perspective. It's 200 hours NOW - and that the company doesn't have budget for. In order to save 400 hours maybe perhaps, if the stars align, two years from now. It's not the same budget. It's not the same time frame. It's not your dept's responsibility. In theory yes maybe but in most businesses, no. These 200 hours now are an investment. This 400 hours maybe perhaps are savings, not profit. They may allow an equivalent 400 hours spent on some profitable new product - but then just ask for budget for the profitable new product, don't worry about where that money comes from. That's sooo far above your pay grade, it's not even funny. If the idea for where to spend the 400 hours is worthwhile, the chairman will raise money to do it. Bring THAT idea to management. THAT would be well received.
In summary: the savings and the new product don't come from the same bits of the balance sheets. They don't affect the future company the same. The wasted 400 hours are already considered in the estimates for the next few years, they are essentially already amortized. They already don't matter. It's not fun for an individual engineer to consider that their work for the next 3 years is financially already long forgotten, lol (?), but basically yes.
It MAY be the right perspective for several levels of management higher up, if people are REALLY working on a 40 year perspective for, I don't know, a mainstream database package, a compiler. But nobody does (in first approximation).
It's also is a good viewpoint where crazy thin differences do make an impact (a refinery).
Still: Most companies that don't plan to be gone in two years do have a methods department or working group. People who do try and make the processes better. They have budget to do that. Bring the idea to them. Hell, even start working part or full time on their budget. But with the understanding that this is yet another group, mission, budget. It's not 200 hours here in exchange for 400 there. And this is a highly technical group - not CXO track except perhaps for a brief stint there.
It was the standard warranty which makes me think there was a known flaw in those keyboards.
Interestingly, I got nowhere with phone support. The support person told me there were no keyboards available and didn't know when it would be back in stock. So then I contacted Dell support on Twitter (as it was known back then) and they immediately got back to me to find out what happened and arranged the repair.
Health insurance in the US, and other countries, is pretty far from traditional insurance markets where you pay a small amount of money to cover rare, catastrophic events (like your house burning down, or an earthquake).
The name might be similar, but the products actually function very differently. Health insurance in many countries covers routine, predictable "losses" like primary care for strep throat as well as long-term "losses" like prescription medication.
A lot of this is because a traditional insurance model isn't palatable when it comes to healthcare. You can't really employ price or service discrimination against high-risk people with preexisting conditions, like you can with auto insuring a Ferrari, or home insuring a coastal house in a hurricane zone.
Not to mention life insurance! You can't just look assume things work the same way because they have similar names.
Apart from ChromeOS, most desktop operating systems default to other browsers. Yet Chrome is estimated to have ~70% of desktop browser market share. So defaults can't be much of a defense against browser advertising, especially on Google-owned properties.
reply