skysight-inc/HackerNews huggingface dataset:
There are a lot of studies of varying quality, some of which show benefit for IVM and HCQ. One place to find some of these compiled is https://hcqmeta.com. Beware that they don't say what their study inclusion criteria is, so one has to be more skeptical of studies that have a small N and/or high P value.

The RECOVERY results for HCQ were definitely negative. Personally I'm neutral on its effectiveness, but HCQ proponents would probably say that HCQ's postulated antiviral mechanism is not effective on already hospitalized patients, since most of them would have already cleared the virus by the time they showed up to the hospital.
It's not belittling; I was considering much the same. My conclusion is that I definitely had anxiety during all those episodes, and the anxiety made the symptoms worse to some extent. My first panic attacks I ever experienced were caused by the symptoms early on when I had no evidence this was going to become chronic and relatively benign. I would be relieved if I could explain away my symptoms as mere hypochondria or acid reflux.

But I persisted for a while in the face of that because I felt that my body was trying to tell me something. Pain is a mechanism we've evolved with to indicate various abnormalities. I was willing to bet there was a reason behind the pain, instead of it serving no purpose whatsoever, and especially because this concerned the region where my heart was located, I felt it was urgent, since my heart is one thing that has to function for me to stay alive.

My unresolved anxiety is that I still haven't found the reason, so there has never been any closure for me. Worse, I might not be getting the treatment I need to prolong my lifespan. It's terrifying when considering that possibility in full, so I've had no choice but to put it out of my mind.

I stopped taking a lot of things about how I'm still alive for granted, but I've actually had start taking many of them for granted again, because if I didn't I would become completely paralyzed by fear for entire days. I had to find the balance between worrying about every potential cause of death I could face within the next hour causing desperation and expending my time being unproductive.

I did at least have a few positive outcomes since then. If it weren't for the constant pain and fear I don't think I would have changed my diet and started exercising as much as I did. The exercise was reassuring in a sense because the pain wasn't correlated with how strenuous it was. But now I try to be more wary about what I put in my body. I just hope it ends up mattering in the end. I wish I didn't have to worry about dying suddenly so often.
If you can't do anything, you also can't do anything bad!
GP should have said "or with co-morbidities".

Digging into the <60yo cohort, it's shockingly uncommon to find one who wasn't obese.

A year of largely ineffective masking hysteria and not one noteworthy public health figure suggested putting down the donut to reduce the risk of death from COVID-19.

We shuttered gyms and discouraged outdoor activity instead.
> If I buy a product from China, are they required to collect sales taxes for Montana? Of course not. So not sure why a business located in a sovereign US state has any obligation to follow laws of some other state in which they don’t operate.

Actually the same rules apply to both. See https://blog.taxjar.com/international-sellers-deal-sales-tax...
Does your API newsletter have an archive of the old ones by any chance? I am trying to go over as much material as I can especially from first hand experience as I am building a fairly involving one.
There are multiple VMs. The JS one does run offline with Node.js (it's one file to implement BQN and one for Node-specific stuff like command-line and filesystem interaction), but it's not designed for speed. CBQN is what you want. EDIT: Just run make, which will pull from a bytecode branch if necessary. It doesn't ship with bytecode, so currently you have to bootstrap once with either dzaima/BQN or Node; at some point I'm sure we'll publish a full release that can be compiled with C alone for bootstrapping.

Further details at https://mlochbaum.github.io/BQN/running.html, and feel free to contact me or join the forums for help getting set up!
> And as a healthy 49 years old, i'm taking my chance with covid and have no plans for vaccination

so you would rather be at between a 1 in 500 and a 1 in 250 risk of dying in your age group + a much higher risk than that of some long covid symptoms that are debilitating/unknown if they will ever get better vs. a 1 in a 1,000,000 chance you get something that might be bad but is likely survivable... I don't understand the anti-vaxxer "logic"
Completely agree. It helped that I have a recurring meeting in Outlook that starts when I leave work, and goes for an hour. I find that this block prevents people from scheduling surprise last minute meetings, and keeps me from working longer than 8 hours a day (I start at 8 AM and go until 4 PM).
Something I haven't seen discussed is what would have happened if the initial shots went to the 20-35 year old crowd (the ones that are out and about, partying, and have a number of super spreaders in that cohort)? Would that have done more to stop the virus spread then to vaccinate the more vulnerable (but already self isolated) people first? This would never be an option politically, but I'd like to know if it would have had a better shot of stopping the virus spread?
I think the problem is more that they don’t understand that it is not a zero sum game of getting vaccinated with a tiny but some chance for adverse side-effects vs going on with life. It is taking a vaccine with 90%+ rate of success with exceedingly small side effects vs having a kind of high chance of getting a virus that has yet again quite a high chance of not being “just a flu” and causing long-lasting (perhaps even for a lifetime) health issues.

Of course we ideally should also take into account the community benefits, but even on a personal level it is a net plus.
I also hang on to an older car for much the same reasons. Every now and then I’ve had a courtesy car from a garage while mine was in for a service, typically something very recent. I almost invariably dislike them.

You could argue that’s because of familiarity. Obviously I like a lot about my car or I wouldn’t have kept it for this long! But truly, it’s not that I don’t think there’s room for improvement on my old car. There have been plenty of advances since its time that I would welcome if I bought a new vehicle: improved efficiency, safety features, practicalities like better external lighting, and so on.¹

For me, those benefits always seem to be outweighed by the horrible state of controls and displays and “infotainment” systems in new cars. They’re cluttered and intrusive and distracting. I’m not sure which is worse, touchscreens that take your eyes off the road, or cluttering the steering wheel with controls for a phone that it is almost never appropriate to be using while driving anyway in my country. Meanwhile, apparently I still have to take a hand off the wheel for a second or two to change gear or switch on various external safety lights. This should have been some sort of meme punchline, not real life.

Between poorly designed controls, the security and privacy problems that seem to be rampant in modern cars, and the sense that EVs might be the future but there are still some big unanswered questions, I expect it will be a few more years before I change to a new vehicle unless some practical consideration forces the issue first.

¹ I’m still waiting for the windscreen that automatically enhances the driver’s full view in low light or poor weather conditions and subtly highlights the required driving line through junctions as directed by the navigation system, but I reckon we’ll have that too before the self-driving flying cars are here.
Location: Pittsburgh, PA (West suburbs)

Remote: yes (have experience) / preferred

Willing to relocate: for the right job, but mostly looking for remote

Technologies: Go (Golang), Javascript, Vue, Postgres, Linux, Android

Résumé/CV: https://sectionfourteen.com/about

Email: anthony@sectionfourteen.com

Website: https://sectionfourteen.com

------

About me: Nearly 5 years experience as a full stack developer. That includes building internal business applications from the ground up (GUI, backend API, and server setup), CLI's, and web sites.

I have a background in graphic design (10+ years), which tends to give me a leg up in GUI development. Not a leetcode wizard by any means, but have been brushing up on my algorithms.

Most of the applications I've built have been of the smaller, monolithic variety. In the spirit of new challenges, and further developing my skill set, I'm quite interested in working on larger, distributed systems.

Currently pursuing full time positions. Not afraid to hop into new technologies.
> I think some of the administrative pain can come from having a 'sandbox' or 'qa' tier beyond dev (which in this case would be customer facing) before production.

Pretty much. It's hard to guess at the reason why without knowing the product, but for whatever reason customers are wanting access to new features/releases before using them. Which likely means that they need to do something on their end every time you release (validation, update internal training/process documentation, etc). And it's causing disruption when things change outside of their control. So they're wanting more control over that change timing, to smooth out the impact of those releases as far as their usage goes.

If your release codebase can only support a single "production" version of a feature at once, you end up having to provision entirely new environments to hold a client back. And again, for every client wanting this. Because the timing they want isn't going to be convenient enough to be the same.

So instead, structure things so that you can run both the old and new version of "the thing" simultaneously in production, and give the client self-service ability to activate the new version when they're ready. That way your production environment itself is able to accommodate these requests and client's can opt-in when they're ready/comfortable to.

The biggest challenge to doing this tends to be architecting your application so you can push releases to the backend independently to releases in the frontend. Which can generally be handled by routing things through middleware that provides a stable response for a given feature version. If the interface is using the latest version, the middleware is basically just a stub that does nothing. But if the interface is using a prior version, then the middleware accepts the request signature of the prior version, translates into what's needed to execute on the new codebase, and returns a response that's consistent with the prior version. It's a few years old, but here's[1] an example of how we handled the data-model aspect of this sort of setup at a prior company

So in effect you're actually upgrading all customers to the new release at once, but from the customer perspective everything still looks/feels/act the same as they're used to until they "upgrade/opt-in" to the new release.

It's a pretty major lift to implement this architecture (particularly on an existing codebase), but maintaining it is easy to incorporate into the regular development process. And completely eliminates the operational and customer management headaches you're having now.

With this architecture, it doesn't really matter if you're running isolated deployments or a multi-tenant architecture. You only ever have a single version of production in both cases. The "sandbox" isn't a new environment, but a new production account that copies over the configuration/setup of their existing one while applying sandbox-like restrictions to it. This gives them a temporary space to prepare for the change so they're prepared when they flip the switch on their primary account.

[1] https://github.com/TomFrost/Vers
We shouldn't study things like that because it will only be used to support antivaxxer arguments /s
> If you want a position that is 100% remote that never requires you to physically leave your home, you're welcome to look for such.

Every job I've had from 2010 to 2021 has been like this. Some had optional but not required in person meetups, some had no meetups. These jobs are not hard to find if you have a good reputation for being effective remotely.
Were you craving food or just...something to do? Personally, I smoke, which is no better but I feel is likely a similar addiction? Gandhi generalized even further, realizing that he was "addicted to experience" - I think about this often.
Frankly, governments have done the world a disservice by speaking before they really had all the information at the start of the pandemic.

They were doing the best they could to manage a crisis that it was their job to manage in an unprecedented situation. If people expected them to have perfect answers and solutions, they had unrealistic expectations.
is this the same irc trying to commercialize the name irc
I didn't say it should, I just summarized what Opera did.
Yes, there are types of roofs that last a long time. Standing seam metal, slate, clay, concrete, and copper roofs all last a long time (50+ years). Asphalt shingles and EPDM flat roofs last 15-25, cedar shakes can last 30+ years.

The long lasting ones are substantially more expensive than asphalt shingles, 3x at a minimum.
at some point you just have to embrace the fact that you're going to get downvoted for writing things like this, and all you can do is trust that a nonzero number of people will see the downvotes-without-replies and that that will give them pause to think
Title doesn't quite fit, how about this instead?

"Privilege escalation with polkit: Rooting Linux with a 7-year-old bug"
The alternative hypothesis is that the phylogenetic tree is wrong. Maybe those two fish actually share a recent common ancestor.
They should do this experiment in space.
No, but I sure backlash against feature discussed here wouldn't be as big if Google's other hand wasn't pushing fake URLs for AMP pages.
Just right clicked a URL in chrome and saw the "Always show full URLs" option.

Mind blown! Never noticed that there.

Amazing! Thanks for the tip.

I would have guessed the situation would be the opposite, easy to set in FireFox, obscured/hidden in Chrome. But apparently not! :)
Given the sheer volume of doses delivered and the capability to detect clotting risks (az, JJ), the fact that clotting risk did not go up with biontech and moderna might throw a wrench into that hunch.

But even then, not seeing an indication of risk within two orders of magnitude of covid itself.
In preferences it’s simply a check box to have it show full URLs in safari all the time.
> You're already assuming at this point that his time involved in this game is potentially a negative. What if it lands him a job?

Fair enough, you're right that I'm showing my biases. I appreciate the feedback.
Yea, this is terrifying
Move Beyond Passwords
Yes I believe Mozilla will not implement FLoC or at least offer a way to turn it off.
yeah, in the 1700s, poor people didnt need siege engines either
People really will gamble on anything...
I'm highly skeptical that bridging is insufficient for most use cases. After all, most Linux-based access points are using standard bridging.
>The tell is your use of the words "misinformation" and "propaganda." People who tend to levy such claims also tend to share more of it

you said it yourself. It is kind of ironically not surprising that you levied the above mentioned claim and actually posted the misinformation and propaganda yourself - see below.

>No, you weren't.

you really don't know, yet you're making with complete confidence such a completely false blatantly contradicting facts[0] statement just because it suits your narrative

>A common false-flag ...

and helps you to advance your agenda. Thus your post is a clear example of misinformation and propaganda. Not sure that you're doing it intentionally, probably you're just caught up in that mob hysteria.

[0] https://news.ycombinator.com/item?id=8860543
The world has always seemed far ruder & far more off-base. In every circumstance. Linus isn't always a good role model for how to behave, but it is enormously relieving sometimes, in a world that feels batshit insane, to hear someone else processing-out-loud their strong reactions.
I don't disagree. But being well-known as a good 100% remote worker will be a high bar for a lot of people. (As is, at least your implication, of relatively short-term stints.) Most of my jobs have been in the ~10 year range.
Post-viral myocarditis / pericarditis usually occurs in the days to weeks (up to about a month, generally) following a viral infection.
I quite agree. I'd wager many of these "reasonable people" eat artisan sourdough baguettes thinking it's any better than doritos.
I went down a similar rabbit hole recently with unbound as a caching resolver, where it appeared to work on my real computers but didn't on phones. I took a pcap and found that my Android 10+ devices were refusing to use the good-old port 53 DNS my unbound jail was serving because it wasn't DoT. Once I set up unbound with real certs _and_ set it as each device's "Private DNS", it worked as expected.

Your issue might be different but I suggest taking a pcap to make sure your assumptions about what is answering a given DNS query are true.
> Conversions from slice to array pointer: An expression s of type []T may now be converted to array pointer type *[N]T. If a is the result of such a conversion, then corresponding indices that are in range refer to the same underlying elements: &a[i] == &s[i] for 0 <= i < N. The conversion panics if len(s) is less than N.

> Note that the new conversion from slice to array pointer is the first case in which a type conversion can panic at run time. Analysis tools that assume type conversions can never panic should be updated to consider this possibility.

WHY! So now we can't trust that the type *[N]T won't panic at runtime when accessed by in-range index values. This should be identified as an unsafe conversion.
Again, for most of the sample in the OP, it isn't the case that consumer basket is unchanged. Most of the world didn't move out of subsistence living until relatively recently. Their consumption basket was basically identical to someone living five centuries ago, and this was true for almost all of the period in question.

It is also interesting to ask: if what you are saying is true, then what do you think economic history is? There are thousands of price series which do what you say is impossible. To a large extent, the data that we have going back to the 15th century (and beyond) is the study of prices and population. All of the products that people consumed then, they consumed now. Saying that shoes have somehow evolved beyond the comprehension of someone living in the 15th century is...odd.

And btw, this makes no difference at all for this question in any functional sense. No-one believes that if you devised some perfect consumer basket that it would show that the dollar actually maintained value...that makes no sense.

Complaining about the change in quality is something that has become very trendy but this is the least relevant part of the problem. It is an issue when you look at certain products (particularly telecoms) but this isn't really relevant for OP.
Physicists Found New Mechanism Enabling Magnetism and Superconductivity Co-Exist
Agree with both of you: I've been planning to do an embedded BQN for Julia (as well as finish my NumPy one), and having found APL.jl in this thread it looks like a pretty good resource. There are some missing syntax features in the compiler that I'd like to finish first.

If anyone else is interested in working on a Julia VM I think this would be a pretty cool project, and a nice way to learn some of how bytecode interpreters are implemented without getting into the weeds in a low-level language. Join the forums and ask about it!
“Crunch” Open Source Texture Compression Library vs. U.S. Patent (2012)
Yeah, I don't like the style of this 'first, download this script; then, execute it'.. and it creates/overwrites files.

Why not tell me to create the necessary files, with some article content around what we're doing and why?

As an article this doesn't seem to offer anything more than a suggestively named GitHub repository with a small readme.
If you think evolution is just selection and mutations, I can see how you'd think it's not enough (even though selection is usually a very strong force that "locks good mutations in place", which can create a compounding effect in chances of an organism's fitness, so a long time of mutations + locking good ones in place should be almost enough to convince you if you do the math). It's been some time since I studied this so I'm just going to write whatever comes to mind.

Maybe a key part of what's missing in your understanding is not so much "micro" genetics but biogeography and population genetics. You'd also want to check simulations and comparisons with real-world data on some models to see how a population evolves to see that it "really works". It's important to understand that there are different models, and for each one there's a set of "forces" and important parameters.

The bigger picture is, it's the whole interplay between mutation, selection, genetic drift, gene flow; things like differences in population size over time and space, migrations, isolation and reconnection, etc. that makes it work. You might also want to take a look into genetic/functional/morphological modularity. I've just skimmed these articles, but they seem relevant:

https://www.nature.com/articles/hdy2010136

https://www.nature.com/scitable/knowledge/library/natural-se...

There's much more but my memory is murky. Ideally you would want to take a course or read a textbook on evolution. A few popsci books are ok (Dawkins, E. O. Wilson).

TLDR: What the other commenter said -- 4 billion years is a very, very, very long time.
Drain a company of managers, and the devs will self organize and save the company. Drain the company of devs, and the managers will desperately try to hire anyone to replace them. Devs are vastly, vastly, more important than management. Any given manager could leave a company and literally no metric would move.
The point is precisely that LePen's platform claims the EU is a net negative because it ignores French interests. By pursuing the old Mitterrandist project of having an EU under French leadership, Macron is trying to negate that platform.

As for the "constantly rolling boulders", I think you're not being objective. Both Switzerland and Britain agreed on a set of rules decades ago, and are now reneging on them. Surely it's their responsibility to find solutions for the new problems they've created? And once solutions are agreed, surely they should implement them? The only answer from the Anglo press is "no, because everyone must accommodate us", which is frankly embarrassingly juvenile. Even inside the UK a lot of people don't agree with this English manoeuvreing, and absolutely everyone in Northern Ireland knew that the Brexiteers' promises were as unrealistic and unrealizable as they turned out to be. The attempt to unload responsibility for their own actions on a third party is like a child shouting "It wasn't me!" when caught with a hand in the jar and jam all over his face.
I should have said there are 2 meanings of antivaxer in this context. One is the kooks who are/were against all vaccines and nother is the people who are suspicious of the covid vaccines. Those groups are separate and must be treated differently

Herd immunity in the general population will probably be impossible unless the areas that reach it choose to lock themselves from the rest of the world
https://www.nytimes.com/2021/05/28/opinion/herd-immunity-cov...