> The problem is more likely a lack of prioritization at the leadership level.
Great. If you're in leadership why would you prioritize a feature making it easier for people to leave your platform when you could instead prioritize a new feature that might generate value for the company?
There's no incentive to make Takeout any better than it is today.
She lost her son of 17 years only 5 months ago. With no additional details, I know where my mind goes.
Edit: whatever article I read said 5 months ago, but that appears to have been written some time ago. Plenty of articles stating that Shane died in Jan/2022:
> This goes on here, on Reddit, Twitter, wherever a discussion about Musk arises. The only difference between HN and Reddit on this topic is that HN is slightly more highbrow, although the same general attacks get repeated here as they do on Reddit.
My casual observation says that HN has become more "Reddit-Like" in terms of low quality and off-topic posting since the whole Reddit API/MOD debacle.
> Are breweries typically insanely profitable? My understanding is they are like a commodity/staples business with tight margins.
I own a bit of a brewery and have learned a bit about the business in the past 7 years.
No, breweries are not insanely profitable. You might think that they are if you simply look at grain to glass and forget about everything in between.
Those in between parts are real estate/rent, equipment, chemicals, packaging costs (equipment, labor, consumables), employees, taproom expenses, marketing, and finally, the worst, distribution expenses.
It's been a fun ride and I'm glad I'm involved, but insanely profitable just isn't the case.
> It is completely unacceptable that the default level of access has become "everything."
Even on Android (and I presume iPhone) where apps ask for/document their permissions requirements, most people just say "Yes" and move along. Most people have neither the time nor the expertise to critically evaluate whether or not an extension needs any of a dozen permissions.
I sympathize, but I have no idea how you can realistically solve this.
> The recruiter had inserted it onto the copy of the CV he sent to them.
It's been a while, but when I doing technical interviews I would give the candidate a copy of the resume that I had and ask them "Before we start, is this your resume? Is everything on it accurate?"