skysight-inc/HackerNews huggingface dataset:
> A median figure is not skewed by high earners at the top.

That’s exactly my point. For “not skewed by” read “reveal the fact that”. Neither averages nor medians tell you much about the shape of the distribution, but the shape does matter.

Also you’re missing my point about education and health care completely. Yes the OECD accounts for their value overall, but that value is very unevenly distributed in the US. Much more so than in Europe. I also made a point about quality as against just spending.
It would be good to see an autopsy, to find out if it's actually the battery that went into thermal runaway, or something else that shorted and dumped all of its energy.

I have no idea how much heavy metals I've been exposed to by inhaling the toxic smoke. I don't know how much smoke my pregnant wife inhaled. I worry how much chemical residue is on my desk, floor, walls, how much is getting recycled by my HVAC system, how much exposure my pets had.

That sort of paranoia doesn't help. In fact it may cause psychosomatic symptoms (nocebo effect). You've probably inhaled far worse if you've ever been to a barbeque, gas station, or just took a walk in one of the more crowded areas of the city.
Yep, ^this, it happens. You 100% deserve compensation. But this is what their insurance is for. The remaining 99000 thousand pairs they sold will surely pay the deductable.
The study FAQ claims:

> What happens if a website ignores an email that is part of this study?

> We are not aware of any adverse consequences for a website declining to respond to an email that is part of this study.

But the email sent out states:

> I look forward to your reply without undue delay and at most within 45 days of this email, as required by Section 1798.130 of the California Civil Code.

So the email very clearly states that there is an adverse consequence for a failure to respond, namely a violation of the California Civil Code.
ah yeah topics...
I basically meant topics.
But having multiple topics for priority is still way harder than lets say the rabbitmq priority stuff or the postgres stuff.
Alas. Nevertheless, from the article:

>“We don’t think every vehicle has this rare manufacturing defect,” General Motors spokesman Dan Flores said. “But we can’t take a chance, so we’re recalling all the vehicles.”

I mean, that comes pretty close to be out of electric car making.

The same should happen to Bose. A total recall of all wireless headphones they ever made would be a good start.

-------

PS: I'm spending more time in headphones than I do in my car; it's fair to hold them to the same standard.
Our common understanding of the concept of morality is something that is universal. We don't accept that there should be a different morality for the king vs. the peasant.
Use a Private Registry in Kubernetes
Don't manufacturers do that already?

Take into account the probability of a costly failure, and increase the price to account for it. And compensate victims to a certain extent, but quietly. I suppose they would fight any publicity of such incidents, since that would have a huge impact on sales, I have read a few such stories, and usually they disappear from the news pretty soon, likely because the victim agreed to be quietly compensated. I could be wrong.
To be correct, ethylene carbonate is not an electrolyte by itself, but a solvent
What benefits do I get if I use Passage instead of Pass?

I get that it uses only one algorithm and does one thing. But that’s not a benefit impacting the end user in practice. Actually, my Pass also uses CV25519. It’s just, one is written in Go, one in C/bash.

Looking at the list of CVEs for SSH, OpenVPN, OpenSSL and GPG, the latter has stood up pretty well. Plus, OpenPGP is a standard heavily audited which is important for interoperability (and arguably security).
Maybe? Your alternative seems to be to let a few people die every now and then, so that some companies can get better margins.
Did you also not notice how it actually does nothing to increase screen real estate?

I have a visual allergy to notches on phones. I just can't fathom how someone can get used to it on a laptop.
My favourite is equipment with user-replaceable 18650's.

It solves disposal, storage and transport problems and it decouples device lifetime from battery lifetime.

Alkalines are nice but produce a lot of waste. Lots of things don't work quite right with rechargeable AAs but I agree, the things that do are perfect also.
D'oh. My eyes. I saw that first . after lightsail as a ,
Replying to this and jen729's comment, which I can't reply to for some reason.

I'm not entirely sure why this got downvoted (bit of a personal gripe with YC (anonymous down voting/spamming without a direct comment).. buuuut

This idea is only 'silly' if you think of it as a large amount of lead lining.

In this day-in-age, I'm sure the idea of a material/substance around it that stops combustion when something like this happens is surely not out of reach.. I'm as far away from a chemical engineer as you can get, but, if it requires oxygen to burn, maybe some incredibly strong substance around it to contain the chemicals if the battery expands. Or some to absorb oxygen around it.

I dunno, maybe I'm incredibly naive, but it feels like something that, if a portion of the companies that manufacturer/use the batteries put effort into something, it's something that could be made _more_ safe in some way?
Thank you for helping the public out!

Now, if you have energy to simply talk to a lawyer, I suspect it's going to be a slam-dunk case (I'm not a lawyer). They shouldn't get away with offering you a new pair of headphones to replace the one that almost killed you, and caused bodily damage.

If someone threw acid on you in the street, it would be considered assault, and they'd spend years in jail if found and charged. We really don't need to let corporations get away with the same.
> It makes the device feel more organic.

Could you elaborate?
I forwarded an email that to legal counsel who is pulling in a privacy team.

Lots of hours wasted.
https://youtube.com/playlist?list=PLFjonLo8gYHIXC35K4Ujrbu6X...

The unanswered question series by Leonard bernstein. Great stuff for studying the evolution of western classical music and its parallels with intellectual movements till the rise of 20th century nihilism.
They already are - at least fish for consumption. About 50 percent of seafood is harvested through aquaculture: https://ourworldindata.org/rise-of-aquaculture
It happened suddenly, and if I wasn't present, it would have taken out my home and killed my pets and possibly my wife.

I highly doubt that, but don't let the paranoia get to you and start thinking of all the bad things that could've happened, because they didn't. In fact, I'd say the fire retardants in the plastic did exactly what they were supposed to do, given that you only mentioned smoke and not actual flames.
The energy densities of modern batteries are a couple factors lower than that of gasoline, and much lower than TNT. Gasoline is incredibly energy-dense, but its energy density is comparable to butter. Do you worry about sticks of butter exploding on you? No, you don't. Gasoline is dangerous because it really likes to evaporate and the mixture of gasoline fumes and air ignites at the slightest provocation. Batteries are dangerous because they can go into thermal runaway from an internal short if the barrier between the electrodes fails. The energy density is not what matters here.
It’s honestly a win-win. You’re getting paid to get better. It’s on their dime and not yours. The inverse of the situation is that you’re expected to churn out shitty code and it’s never fast enough. Thing break constantly and you never learn how to craft quality code. I’m in the same boat where I’m expecting the PR process to be rigorous. And at the end of the day I can tell the difference between the correct and elegant solution and what’s halved assed but gets it done. At the end of the day I want to be a craftsman where the art of the craft is clean correct software solution. You’re lucky to be in a position where code quality trumps all.
This battery is not small at all, I was astonished how big it is in my B&O headset. Here is a short video showcasing it: https://www.youtube.com/watch?v=xeKc4GZwcIo
Eric Clapton successfully sues a woman selling a Bootleg Live CD on eBay for $11
Yeah because you all want money for it.

Insurance in America is famously expensive. Does anyone ever wonder why?

I live in Australia. If I tripped on the kerb and broke my leg I’d go to the hospital and it’d get fixed for free and that’d be the end of it.

If that happened in the US you’d go to the hospital, the bill would be $50k, you’d sue for $50k, and you’d bitch that your insurance was too high!
> rust decided not to go down the route of implementing user space threads

Rust had (optional) user-space threads a long time ago, but that was removed in the pre-1.0 days as it added a lot of complexity and had some unavoidable performance loss even when opting for native threads (it forced dynamic dispatch on anything related to threading or I/O). There was a lot of discussion here but eventually it was declared that the OS thread scheduler was in fact perfectly capable of handling large numbers of threads and that virtual memory mapping meant the stack space allocation for each thread wasn’t a big deal and so green threads were removed.
There are other teams than corporate IT teams. There are other non technical groups that would greatly benefit from e2e groups like Signal has, that would love the added luxury of self hosting/non centralised hosting.
I can easily envisage different groups wanting these things.

Some do not want the 'historical' chats to be kept, & server side search is not really relevant in those cases. Of course, some will.

If we think of more than tech teams, it's easy to see these features as being vitally important. So while bugtracking, CI, bots, etc, etc is important for you and I, there are groups and communities where such things would be met with bafflement as to their purpose.
There is a bug report for that. It's not been moving at all since it was opened https://github.com/mozilla-mobile/fenix/issues/2371
A few comments:

1) Why shouldn't one be compensated for a faulty product? Considering all we have is the OP's word for it, it appears that there was no faulty use and the product (whether the entire product line or that individual set of headphones) likely had some issue. You say it was an "accident", as if it were some act of God and not an act of physics.

2) Yes, Americans are crazy on independence, apparently you have a different definition for the word. Independence doesn't mean that people can push out faulty products and the populace just has to deal with it. Independence does not mean no one takes responsibility for issues they cause.

3) The American system is much better than what I have seen in the rest of the world where you can just push out faulty medicine or have faulty surgeries, for example, maim people and then get away with paying them some meager $20k total, forcing them to rely on public services and pushing them to borderline poverty for life.
Not being required to share your real phone number with other endpoints is a big security feature for Telegram beyond anything to do with encryption.
Scary. Are we, as the consumer, pushing for safer batteries? Is there a shut-down mechanism available for lithium battery faults?
Nobody did die though, nor is it very likely they would. And this is one pair out of however many million they've sold. I'm not arguing there shouldn't be compensation in this instance, nor an investigation into why it happened. But hypothetically if it was some one in a million space particle (which is obviously unlikely), I think it's pretty ludicrous to expect Bose to design for that eventuality.
What do you mean by "with storage"? How much of it? If you want to cover for an 8-hour windless night, at 1 GW, you will need 8 GWh of storage, and you will need to generate a surplus of 8 GWh of electricity during the remaining 16 hours of the (previous) day, every day (windy or not, sunny or not).

Comparing solar/wind to nuclear requires more elaboration than just slapping a "with storage."
There were 4 shootings in a span of 10 days at CHOP (the entire thing lasted 23 days and covered 6 blocks). A 16 year old and a 19 year old were killed and four other people were shot, including a 14 year old. That's "not that bad"?
No, lithium battery fires are really nasty, and that's why he got a chemical burn.

LiPF6 is a contact irritant, PF5 it decomposes to is a gas, and also a respiratory irritant, and HF PH5 decomposes in the air is a dangerous poisonous acid.

This is what everybody visiting a lithium battery factory is told on safety orientation. In case there is fire in the factory, run, preferably until you are few blocks away.

If enough hot aqueous LF6 in solvent gets on the skin, you will get a chemical burn. In worst case, the same thing as HF poisoning will happen (it pulls electrolytes out of blood, and then death from heart failure.)
> But if the statement was true and accurate I would just take it as a helpful reminder of the timeframe.

No. Absolutely not. A helpful reminder of the timeframe would be "the deadline for our study is ..., please try to send your response by then if you wish to be included."

Quoting legal code is not at all a helpful reminder of a timeframe, but is a direct implication of legal ramifications for failure to comply.
Have a look at insurance premiums that doctors have to pay, especially the high-risk specializations (like neurosurgery). I guess I don't have to explain why they're so high.
You're not really gaining them either. In full screen, apps are basically the same as they were previously since the top notch bar becomes blacked out. In regular mode, they've increased the vertical height of the menu bar to match the notch, so there's what, a handful of pixels gained there?
I think it helps if a team considers everything to be temporary, and code reviews are more for understanding how things work, with some some captured discussion of how it could be re-done. The author should merge, declare victory, and move on, while someone else re-writes it to their liking. It shouldn’t be considered done until it’s been re-done twice by separate authors.

One thing I’ve realized about software “engineering” is that it’s layered thick with opinions. If you force your opinions on someone, they check out and you get nothing of value from them. It’s probably better just to let them do things their way, and find the place where they can add the most. Some architects think their job is to walk around the beach kicking sand castles.
>There is an annoying trend among people that expect everything to be perfectly safe. It seems to be a symptom of an overly sheltered existence.

Yeah, how overly sheltered to not expect your headphones to not catch on fire and kill you. It's a symptom of not believing when someone pisses in our eyes and tells us it's raining. Especially when it's happening on our own dime.

>Nothing is perfectly safe, that is how lithium batteries fail.

Then lithium batteries should be banned from headphones.

>You should know so you can properly deal with problems.

Good point! And where would the customer learn about this? From HackerNews?

Last time I checked, Bose devices didn't come with a self-combustion warning.

And until they do, my point applies.
Ignoring how accurate calling it RF is, so the experiment showed that electrons travel faster through air than through copper, you can see that, and the two delays are what you'd expect them to be?
What is the one thing people can do to make their website better? EoY CSSTricks
That is commonly caused by bad contacts, which have a high resistance and thus dissipate heat, which then leads to higher resistance, more heat, etc. The tendency of manufacturers to make each generation of connector smaller and with more fragile contacts, for aesthetic reasons, certainly doesn't help.
> If someone threw acid on you in the street

Intentionally?
> Looking at the website of Remix [2] itself, it feels a bit weird. I may be missing something, but it feels like what Remix offers is what traditional server-side rendered HTML already does.

Ah but they've managed to make what's old new again - and hype it to a level getting on for when Rails was first introduced...
>You act as if this is some new phenomenon, but it's just the latest data point in a dangerous game played by both sides.

Your list supporting "both sides", when in chronological order, starts with three instances in a row of Republicans attacking the legitimacy of Democrats, the third one of which (birtherism) was driven by Trump!

If you're going to spin this as both sides, you can spin it better than that.

For instance, I'm pretty sure that the hatred for the Clintons, at least in the 90s, had a lot to do with Hillary's association with Watergate. So in the minds of Republicans at the time, I believe they felt it was payback for making Nixon resign.
Adidas’ not Nike’s.
I contribute monthly to https://noyb.eu/ and am following their initiatives in that regard [1].

[1] https://noyb.eu/en/project/advertising-ids
Have you ever considered that the bodily want and need to consume more carbs might not be something that's just inherent in us and might be caused by external factors?

Do you understand not everyone experiences hunger in the same way?

Have you also considered the fact that carb heavy food is generally so much cheaper than when it's not?

This is what I mean by its complex.

Carb addiction is real and the solution isn't to make people feel like shit about it and actually help them overcome it and then study why the addiction is becoming more common place. We've added so much random crap to our bodies and food intake, and any number of them can interfere with our natural hunger and food-seeking process.

So yeah, even if carbs are causal, telling people to eat less is not helpful.

Thankfully, we are now getting medication that directly addresses this feeling of extreme hunger that a lot of obese people experience. The causes of those feelings is still being studied.
> As for covering things up, that's a specialty of this field, as any former nuclear insider will tell you.

We do not know the same "insiders in the field" then.

As a former electrical engineer, many of my friends works for EDF in Nuclear. And none of them ever talk about covering things up.

It is quite the opposite, any minor incident generally trigger a ton of process and often a partial shutdown "just in case".

Every possible interaction with the installation is documented, planned and part of a process with X layers of human verification before any intervention.

I do not know how the nuclear industry run in other countries but that is not the culture for EDF to cover things up. For politicians with their own agenda, it's an other story....
its unreachable
Some email providers block email from networks they consider spammy. Just drop them on connect, never accept the delivery. I can't get email from Linode to Outlook 365 for love nor money.

I wouldn't be entirely surprised if DO had the same problem from time to time, if they deliver direct from their own network.
It’s extremely important if you’re a white or Asian applicant whose parent didn’t attend or donate a large sum of money to Harvard.
> Most senior+ engineers that I know would hear that and recoil. Getting "clever" with concurrency handling in your home-rolled queuing system is not something that coworkers, especially more senior coworkers, will appreciate inheriting, adapting, and maintaining. Believe me.

I am both a "senior+ engineer" that has inherited such systems and an author of such systems. I think you're overreacting.

Concurrency Control (i.e., "lock semantics") exists for a reason: correctness. Using it for its designed purpose is not horror. Yes, like any tool, you need to use it correctly. But you don't just throw away correctness because you don't want to learn how to use the right tool properly.

I have inherited poorly designed concurrency systems (in the database); yes, I recoiled in horror and did not appreciate it. So you know what I did? I fixed the design, and documented it to show others how to do it correctly.

I have also inherited OOB "Queuing Systems" that could not possibly be correct because they weren't integrated into the DB's built-in and already-used correctness system: Transactions and Concurrency Control. Those were always more horrific than poorly-implemeneted in-DB solutions. Integrating two disparate stores is always more trouble than just fixing one single source.

----

> I get that you're trying to flex some cool thing that you built, but it doesn't really have any bearing on the concept of "most cases" because it's an anecdote. Queuing systems are a thing for a reason, and in most cases, using them makes more sense than writing your own.

I get that you're trying to flex that you use turnkey Queueing Systems, but it doesn't really have any bearing on the concept of "most cases", because all you've presented are assertions without backing. Queuing systems are good, for a specific kind of job, but when you need relational logic you better use one that supports it. And despite what MongoDB and the NoSQL crowd has been screaming hoarsely for the past decade, in most cases, you have relational logic.
> the argument is “it’s ruggedly impractical for ordinary citizens of any country to parse the laws of other countries”

Julian Assange and Kim Dotcom and myriad less famous individuals will be relieved to hear it.
>Don't manufacturers do that already?

Yes they do, and this is why we have CPSC and lawsuits: to increase the cost of failure to the point where it's not a wise business decision to allow one to happen.

Nothing is 100% fool-proof, but the difference between 99.9% safe and 99.99% safe is 10x decrease in incidents.
Breed isn't extremist. In San Francisco politics, she's a tad right of center. Indeed, the Board of Supervisors "progressive" caucus replaced her as acting mayor in early 2018 with Mark Farrell in a failed effort to torpedo her campaign for the coming mayoral election.

Here's the very left supervisor Hillary Ronan describing Breed in 2018: "The same rich white men that steered the policies that have created the mess we are in today are the same people who are firmly behind the candidacy of London Breed." (https://beyondchron.org/sfs-twisted-racial-politics/)

Now, the progressive left is an extremely powerful force in the city, though not quite a majority. No mayor, whatever their political views, could get anything done without understanding how to placate that group. That's how politics works--you have to compromise to get anything done. Unfortunately, like Republicans nationally, local progressives have learned how to abuse that dynamic by using obstructionism and extreme rhetoric to pull the center of debate in their preferred direction. And that's how the city ends up with some of its more extreme policies and general paralysis.
It is an issue but that issue has to be solved by different means than having fact-checkers saying that BMJ is wrong. BMJ clearly states at the top of every page that it is meant for healthcare professionals.
It's hard to work with people who see the code review space as a battleground. I think the problem is not the overdoing but the problem may be the purpose.
Sexual health promotion messages for young people in Netflix most-watched series
>So a reasonable member should be able to get any sort of interesting or at least non-insane paper in there, by judicious choice of colleagues for review.

An easy way to go get interesting papers in does not seem like a reason to be 'down' on it.