plant lover, cookie monster, shoe fiend
16911 stories
·
20 followers

Has COVID set us up for a major heart disease epidemic? It’s happened before

1 Share

Over the first half of the 20th century the world saw growing rates of heart disease mortality. From the 1920s to the 1960s more and more people were dying from heart attacks. It was described as an epidemic of heart disease. But in the mid-1960s heart disease mortality suddenly plateaued.

In the United States, for example, around 35% of overall deaths could be attributed to cardiac causes in 1966. From that point on heart attack mortality began to dramatically drop. By the mid-1990s overall deaths in the United States due to cardiac causes was almost half of what it was 30 years prior.

This rise and fall of heart disease mortality in the 20th century still remains a mystery to researchers. The numbers can’t be explained by improvements in medicine and medical care. In fact, as rates of obesity increased in the later part of the century and processed food became more unhealthy, heart disease mortality realistically should have continued to rise.

One researcher, writing about the mystery in 2012, suggested the decline of the 20th century heart disease epidemic cannot be effectively explained by dietary or physical factors. Instead, there must be an unknown environmental biological factor at play.

"The epidemic is now virtually at an end, but we are left with the question, has CHD [coronary heart disease] been due to an environmental biological factor, which is a micro-organism, a bacterium or a virus? If so, it has not been clearly identified, but it has never been fully investigated," writes D.S Grimes.

Fallout from the flu pandemic

Around 20 years ago a pair of epidemiologists presented a controversial new hypothesis to explain this weird phenomenon: the 1918 influenza pandemic triggered a wave of heart damage in millions of people and primed them for later-life heart disease.

The research suggested a decline in H1N1 influenza activity over the decades following the 1918 pandemic correlated with a later drop in cardiac mortality. The hypothesis was that a combination of the virus circulating less and potential changes to the way the disease affects cardiovascular health in a host led to the overall decline in heart attack deaths over the later decades of the 20th century.

Unsurprisingly, this hypothesis has been fiercely debated by researchers over the past couple of decades. A detailed dig into the epidemiological data in 2016, from a trio of US researchers, found the connection between the 1918 pandemic and trends in mortality to be, “not congruent with the available data on long-term changes in heart disease mortality.”

In other words - yes, there has been a dramatic rise and fall in heart disease mortality over the 20th century but, no, it is unlikely to be related to the 1918 flu pandemic.

More recently, epidemiological research has focused explicitly on the possible long-term effects of prenatal H1N1 exposure during the 1918 pandemic. Here, researchers looked specifically at what happened in the long-term to those either still in the womb or just born around the years of 1918-19.

A compelling 2009 study compared the 1919 birth cohort to those born just before or just after the period of the acute pandemic. Across a variety of benchmarks the researchers found significant long-term health complications were more prominent in the 1919 cohort. After the age of 60 the 1919 cohort were found to have 25% more incidences of heart disease, plus lower levels of educational attainment compared to other cohorts.

“The fact that this cohort of people had elevated risks of disease even more than six decades after the pandemic indicates that maternal exposure to the influenza virus appears to have had wide-ranging and long-lasting health effects on offspring,” said Eileen Crimmins, one of the co-authors on the study, in a 2020 interview.

These studies are, of course, subject to a whole host of limitations, not the least of which being they can only look at overall population trends and not actually quantify which children were directly exposed to influenza while in the womb and which were not. The conclusions are based on the idea that the virus was so prevalent during 1918/19 that it is likely most babies were exposed.

Interestingly, the data is not limited to US birth cohorts. Subsequent studies have looked at long-term outcomes from birth cohorts born during the flu pandemic in both Taiwan and Sweden. Similar patterns were noted from increased rates of long-term health problems to lower levels of educational attainment.

Human hearts meet SARS-CoV-2

SARS-CoV-2 is a very different virus to influenza. In many ways it is much more problematic. It can infect a far wider assortment of human organs and tissues than influenza and it is mutating in ways very different to H1N1.

The COVID pandemic has not waned and dissipated in the same way the 1918 pandemic did. Instead, the SARS-CoV-2 virus is frantically changing its form from month to month leading people to experience relatively frequent reinfections. This constant exposure to the virus may be amplifying its long-term impact, but of particular interest is the potential impact this could have on our hearts.

A recently published study from Japanese researchers laid out exactly how SARS-CoV-2 can infect and damage the heart. The researchers concluded with a stark warning: we may be facing a looming heart disease epidemic over the coming decades.

In order to infect someone the SARS-CoV-2 virus first needs to track down cells harboring a particular kind of enzyme. Called ACE2, this enzyme acts a bit like a doorway into the cell for a coronavirus. The virus’s spike protein binds to ACE2, allowing the pathogen a pathway into the cell’s inner machinery.

In news that will surprise nobody, ACE2 receptors are all over the epithelial cells that line our nose, mouth, lungs and airways. This is how COVID manifests in the illness that most people are now quite familiar with.

But ACE2 receptors are not isolated to those particular respiratory cells. ACE2 can be found all over the body in a wide variety of organs – and this receptor is found in relatively high volumes on cells inside our heart.

Early warning signs

Early on in the pandemic doctors started to see a significant uptick in patients presenting to emergency rooms with acute heart problems. In the first eight weeks of the pandemic hitting New York City in early 2020 paramedics had to deal with three times the rate of nontraumatic out-of-hospital cardiac arrests compared to the same time period in 2019. Similar data was coming out of other regions hit in the earliest phase of the pandemic. In Northern Italy, for example, out-of-hospital heart attacks spiked by 58% across those initial months in 2020.

An early warning report from a team of doctors in New York City published in April 2020 noted distinct signs of heart tissue injury in a number of deceased COVID patients. This virus was doing something to our hearts.

As more time passed, and longer-term studies accumulated, it became clear that SARS-CoV-2 infections notably affected a person’s heart health. Waves of infections correlated with waves of heart attack deaths. In the 12 months following a bout of COVID people were five times more likely to suffer from myocarditis and twice as likely to experience a heart attack. Even recovered COVID patients were showing longer-term signs of heart damage.

But why were people facing a persistent risk of heart disease in the months, and perhaps years, following a case of COVID? Could a short-term infection with SARS-CoV-2 be causing a kind of long term damage to heart tissue that elevates one’s risk of cardiac complications?

Possibly. But another hypothesis started to emerge. Maybe the virus was becoming a latent infection – sitting quietly in heart tissue and slowly degrading a person’s overall heart health?

The lingering virus

To investigate this idea, a team of researchers, including Hidetoshi Masumoto and Kozue Murata from the RIKEN Center for Biosystems Dynamics Research, created a three-dimensional cardiac model in the lab using human-induced pluripotent stem (iPS) cells. This led to what the researchers describe as a “vascular network-like structure that morphologically and functionally mimics the human heart.”

The cardiac tissue model was then infected with SARS-CoV-2 and the researchers found the infection effectively persisted for up to 28 days. Most interesting, however, were the experiments with only mild or moderate viral exposures. In these cases, the researchers saw cardiac function recover from any initial abnormalities within a month. But the virus remained present in the heart tissue despite causing any observable dysfunction.

“The relationship between the severity of acute illness and persistent viral infection in the heart tissue is indirectly suggested by experiments conducted in the paper using various viral titers,” explain Masumoto and Murata in an email to New Atlas. “In other words, if exposed to a very high viral load during the acute phase, it may lead to fatal acute cardiac infection rather than persistent infection. Conversely, infection with a milder viral load may result in the virus lingering in the heart without causing heart dysfunction, indicating the potential for persistent infection.”

Then, to mimic what happens in a human heart in cases of acute ischemic heart disease, the researchers exposed their cardiac model to hypoxic stress. This simulates a scenario where heart tissue struggles to meet increased oxygen demands.

The experiments found heart tissue with a persistent SARS-CoV-2 infection showed significantly increased dysfunction when exposed to stress compared to uninfected cardiac models. This was despite the infection being so mild that there was no identifiable day-to-day dysfunction.

“Our findings suggest that patients with persistent SARS-CoV-2 infection may be more susceptible to developing heart dysfunction compared to non-infected individuals in the face of these increasingly prevalent diseases,” Masumoto and Murata say. “Ischemic heart diseases fundamentally arise from an imbalance between oxygen demand and supply to the heart. Therefore, situations where oxygen demand in the heart increases rapidly, such as excessive exercise, might potentially create similar stress conditions on the heart.”

It’s important to note that there are many unanswered questions right now. It is only speculation to suggest this lab model of persistent SARS-CoV-2 infection in heart tissue is responsible for the noted real-world increases in cardiac events following COVID. It is also unclear how often infections lead to persistent infiltration of heart tissue. Does vaccination reduce one’s likelihood of a persistent infection? Do we all have some trace of SARS-CoV-2 in our heart tissue now, or is it just some of us? And perhaps most significantly, do frequent reinfections increase the chances of a persistent infection in heart tissue?

Masumoto and Murata call their findings a “warning for the possibility of a heart failure pandemic in the post COVID-19 era.” They are also cautious of not being unnecessarily alarmist. They suggest these potential heart health issues can be mitigated if we work now to recognize and understand what is possibly happening.

“We're not suggesting an undue fear of SARS-CoV-2 in our research,” Masumoto and Murata add. “Rather, we propose coexistence with SARS-CoV-2 in the post-COVID-19 era. We hope that our research results will advance the development of diagnostic and treatment methods for persistent cardiac infection, enabling coexistence between the novel coronavirus and humanity.”

So what now?

If the 1918 flu pandemic caused a noticeable spike in heart disease over the following 50 years then what could a virus with a greater propensity for heart infiltration like SARS-CoV-2 cause?

There are too many unknowns to truly understand what the long-term effects of the COVID pandemic will be. And realistically, we will only clearly know decades from now if a few bouts with SARS-CoV-2 in 2020 and 2021 can lead to increased chances of heart disease in later life.

But we do know some things for sure. We know that viral infections can play a role in the development of heart disease. We also know that SARS-CoV-2 can affect the heart in ways that are relatively unique to coronaviruses. And we certainly know that over the first few years of the pandemic there has been a distinct increase in fatal cardiac events.

There are also some things we don't know for sure but have suspicions about. It is possible the 1918 flu pandemic triggered a century of poor health outcomes in its survivors. It is also possible the SARS-CoV-2 virus can lead to latent infections in the heart.

Eileen Crimmins, an demography expert and professor at USC Leonard Davis School of Gerontology, is clear in stating the possible long-term concerns of this COVID pandemic.

“I think that COVID is setting us up for a hundred years of problems.”

Read the whole story
sarcozona
24 minutes ago
reply
Epiphyte City
Share this story
Delete

The WHO's claim that COVID wasn't airborne cost millions of lives. Now, they're changing the definition of airborne.

1 Share

Create your profile

Only paid subscribers can comment on this post

Check your email

For your security, we need to re-authenticate you.

Click the link we sent to , or click here to sign in.

Send this story to NewsBlur
Shared stories are on their way...
Read the whole story
sarcozona
30 minutes ago
reply
Epiphyte City
Share this story
Delete

Government hits Canada Life with financial sanctions | CBC News

1 Share

The federal government has begun imposing financial sanctions on Canada Life after months of outcry from public servants, retirees and their families who were left fighting for medical claims to be covered.

Public Services and Procurement Canada (PSPC) said it "is taking steps to address startup delays faced by Canada Life and has begun to apply financial consequence mechanisms under the contract," according to a statement from spokesperson Michèle LaRose.

She said PSPC is not yet in a position to share details about the nature of the sanctions.

On July 1, 2023, the federal government transferred responsibility for the public service health insurance plan from Sun Life to Canada Life.

The company had a six-month transitional period before the government could begin assessing the level of service, according to tendering documents for the $514-million contract. 

For months, the federal government has repeatedly stated that it's prioritizing collaboration with Canada Life to improve service, before resorting to financial penalties or withholding payments. 

During that time, CBC News heard from several members of the Public Service Health Care Plan (PSHCP) complaining of long waits, failing to get through to an agent and claims denied without explanation. 

A spokesperson for the Professional Institute of the Public Service of Canada (PIPSC) said she hopes the sanctions will serve as a warning to motivate change, but said they're only a first stab at fixing what's wrong.

"These sanctions really are only to acknowledge the fact that Canada Life is not respecting its contract," said Stéphanie Montreuil. 

"It is not compensating our members. It is not ensuring that there's a plan in place so that this does not continue to happen, so it really just is a start — and the bare minimum at that."

Canada Life says early challenges 'resolved'

A Canada Life spokesperson said on Wednesday that early challenges related to the transition "have been resolved."

"Canada Life is delivering benefits under this plan in Canada within expected service levels, including answering calls within 30 seconds and processing electronic claims within 1 day on average," the spokesperson wrote in an email.

The president of the Professional Association of Foreign Service Officers (PAPSO) said her members are frustrated and angry about delays in coverage outside Canada.

Pamela Isfeld welcomed the news of sanctions as "a positive step," but said the government is still responsible for actually fixing the underlying problem. 

"As a taxpayer, I'm happy to learn that they are not going to continue to just keep paying this very lucrative contract, even when they're not receiving the service," she said.

"But as the representative of 2,000 foreign service officers here in Canada, we still have the same problem with the lack of an adequate health insurance plan, especially abroad and especially in the U.S. where the problems are the worst," Isfeld added.

"That still needs to be fixed."

Subcontractor MSH International handles the international side of the plan, including emergency travel coverage and comprehensive coverage.

As far as PSPC is concerned, though, the ultimate responsibility still rests with Canada Life.

"As the contractor for this project, Canada Life is responsible for ensuring that all deliverables set out in the contract are met, including work that is subcontracted out to other companies," LaRose said.

Struggle to get claims covered abroad

Isfeld said delays in processing member claims and those of family members are "enormous."

"In some cases, it's a question of large sums of money, and when the refund comes, there's just some amount in their bank account. It doesn't match the amount claimed and there's no explanation," she said in French.

That's what happened to Sonia Rioux, who lives in Europe with her military spouse. She was waiting for a refund for medical costs from a trip to Australia in July.

The couple was in a remote region preparing for a hiking excursion when Rioux began suffering abdominal pain. It was getting worse and worse, so she went to a clinic where nurses decided to send her to the closest hospital by air for an emergency operation.

She estimates the total cost at more than $8,000. It was the end of her trip — but only the beginning of her struggles with MSH International.

Rioux said she began her claim with MSH International at the end of August. In mid-April, she received a refund of about $2,000, without any clarity on which bill was being covered.

Rioux said she feels powerless and trapped because nothing she's tried seems to work, leaving her with "no escape."

"It becomes almost anxiety-inducing," she said in French. "I won't give up, but I find it exhausting."

Unions looking at legal remedies

PAFSO has decided to follow the example of the Public Service Alliance of Canada (PSAC) and study all possible legal remedies to force the government to provide a functioning health plan.

"It's the responsibility of the employer, and it's time they find a way to fulfil it," said Isfeld. "We haven't ruled out any legal options at this point. Everything is on the table."

PAFSO's lawyers are studying whether it would be possible to get a ruling forcing the government to put in place a temporary system that would allow employers to take out private insurance, she explained.

The union has also filed a policy grievance with the Treasury Board. The document obtained by Radio-Canada states that the switch to a new insurance provider violates the collective agreement because it "doesn't take account of the members' rights to a functioning health insurance system."

PSAC, Canada's largest public sector union, filed a similar grievance in February.

The two unions are demanding all affected public servants be compensated for the harm they've suffered including stress and pain, as well as financial losses.

PSAC national president Chris Aylward said in a written statement he encourages all its members to file individual grievances to put pressure on the employer.

Montreuil said PIPSC is now in the process of submitting a grievance.

Government 'working daily' with insurer

The federal government said it is still following up with Canada Life to ensure it meets its contractual obligations.

"We are working daily with Canada Life to make it understand that the company it subcontracted for international coverage must improve the situation and ensure that contractual obligations are respected to the letter," Treasury Board President Anita Anand said in a written statement.

"All public servants deserve the highest quality of service for their healthcare plans."

Treasury Board Secretariat spokesperson Joie Huynh noted that Canada Life has taken several measures to improve service since November, and that there have been "important improvements in wait times and processing delays."

She added that Canada Life is working with MSH International to put in place an action plan for international insurance coverage.

Employees of Global Affairs Canada who are living abroad can also count on interest-free cash advances from the government to cover medical costs until they can be refunded by MSH International.

A Canada Life spokesperson said in an email that the company working with MSH International and the federal government to improve the level of service for public servants and retirees living or travelling abroad.

MSH International's program delivery director, Jina Park, said the company has put in place measures to speed up processing times, reduce call centre wait times and prioritize urgent cases.

"We have doubled our claims processing capacity and continue to add more staff to meet demand that was higher than projected in the RFP," she wrote in an email.

Pamela Isfeld is the president of the Professional Association of Foreign Service Officers.

Read the whole story
sarcozona
3 hours ago
reply
Epiphyte City
Share this story
Delete

Firstyear's blog-a-log

2 Shares

At around 11pm last night my partner went to change our lounge room lights with our home light control system. When she tried to login, her account couldn't be accessed. Her Apple Keychain had deleted the Passkey she was using on that site.

This is just the icing on a long trail of enshittification that has undermined Webauthn. I'm over it at this point, and I think it's time to pour one out for Passkeys. The irony is not lost on me that I'm about to release a new major version of webauthn-rs today as I write this.

The Dream

In 2019 I flew to my mates place in Sydney and spent a week starting to write what is now the Webauthn library for Rust. In that time I found a number of issues in the standard and contributed improvements to the Webauthn workgroup, even though it took a few years for those issues to be resolved. I started to review things and participate more.

At the time there was a lot of optimism that this technology could be the end of passwords. You had three major use cases:

  • Second Factor
  • Passwordless
  • Usernameless

Second Factor was a stepping stone toward the latter two. Passwordless is where you would still type in an account name then authenticate with PIN+Touch to your security key, and usernameless is where the identity for your account was resident (discoverable) on the key. This was (from my view) seen as a niche concept by developers since really - how hard is it for a site to have a checkbox that says "remember me"?

This library ended up with Kanidm being (to my knowledge) the very first OpenSource IDM to implement passwordless (now passkeys). The experience was wonderful. You went to Kanidm, typed in your username and then were prompted to type your PIN and touch your key. Simple, fast, easy.

For devices like your iPhone or Android, you would do similar - just use your Touch ID and you're in.

It was so easy, so accessible, I remember how it almost felt impossible. That authentication could be cryptographic in nature, but so usable and trivial for consumers. There really was the idea and goal within FIDO and Webauthn that this could be "the end of passwords".

This is what motivated me to continue to improve webauthn-rs. It's reach has gone beyond what I expected with parts of it being used in Firefox's authenticator-rs, a whole microcosm of Rust Identity Providers (IDPs) being created from this library and my work, and even other language's Webauthn implementations and password managers using our library as the reference implementation to test against. I can not understate how humbled I am of the influence webauthn-rs has had.

The Warnings

However warnings started to appear that the standard was not as open as people envisaged. The issue we have is well known - Chrome controls a huge portion of the browser market, and development is tightly controlled by Google.

An example of this was the Authenticator Selection Extension.

This extension is important for sites that have strict security requirements because they will attest the make and model of the authenticator in use. If you know that the attestation will only accept certain devices, then the browser should filter out and only allow those devices to participate.

However Chrome simply never implemented it leading to it being removed. And it was removed because Chrome never implemented it. As a result, if Chrome doesn't like something in the specification they can just veto it without consequence.

Later the justification for this not being implemented was: "We have never implemented it because we don't feel that authenticator discrimination is broadly a good thing. ... they [users] should have the expectation that a given security key will broadly work where they want to use it."

I want you to remember this quote and it's implications.

Users should be able to use any device they choose without penalty.

Now I certainly agree with this notion for general sites on the internet, but within a business where we have policy around what devices may be acceptable the ability to filter devices does matter.

This makes it very possible that you can go to a corporate site, enroll a security key and it appears to work but then it will fail to register (even better if this burns one of your resident key slots that can not be deleted without a full reset of your device) since the IDP rejected the device attestation. That's right, even without this, IDP's can still "discriminate" against devices without this extension, but the user experience is much worse, and the consequences far more severe in some cases.

The kicker is that Chrome has internal feature flags that they can use for Google's needs. They can simply enable their own magic features that control authenticator models for their policy, while everyone else has to have a lesser experience.

The greater warning here is that many of these decisions are made at "F2F" or Face to Face meetings held in the US. This excludes the majority of international participants leading some voices to be stronger than others. It's hard to convince someone when you aren't in the room, even more so when the room is in a country that has a list of travel advisories including "Violent crime is more common in the US than in Australia", "There is a persistent threat of mass casualty violence and terrorist attacks in the US" and "Medical costs in the US are extremely high. You may need to pay up-front for medical assistance". (As an aside, there are countries that have a "do not travel" warning for less, but somehow the US gets a pass ...).

The Descent

In 2022 Apple annouced Passkeys.

At the time this was just a really nice "marketing" term for passwordless, and Apple's Passkeys had the ability to oppurtunistically be usernameless. It was all in all very polished and well done.

But of course, thought leaders exist, and Apple hadn't defined what a Passkey was. One of those thought leaders took to the FIDO conference stage and announced "Passkeys are resident keys", at the same time as the unleashed a passkeys dev website (I won't link to it out of principal).

The issue is described in detail in another of my blog posts but to summarise, this push to resident keys means that security keys are excluded because they often have extremely low limits on storage, the highest being 25 for yubikeys. That simply won't cut it for most people where they have more than 25 accounts.

Now with resident keys as passkeys as users we certainly don't have the expectation that our security keys will work when we want to use them!

The Enshittocene Period

Since then Passkeys are now seen as a way to capture users and audiences into a platform. What better way to encourage long term entrapment of users then by locking all their credentials into your platform, and even better, credentials that can't be extracted or exported in any capacity.

Both Chrome and Safari will try to force you into using either hybrid (caBLE) where you scan a QR code with your phone to authenticate - you have to click through menus to use a security key. caBLE is not even a good experience, taking more than 60 seconds work in most cases. The UI is beyond obnoxious at this point. Sometimes I think the password game has a better ux.

The more egregious offender is Android, which won't even activate your security key if the website sends the set of options that are needed for Passkeys. This means the IDP gets to choose what device you enroll without your input. And of course, all the developer examples only show you the options to activate "Google Passkeys stored in Google Password Manager". After all, why would you want to use anything else?

A sobering pair of reads are the Github Passkey Beta and Github Passkey threads. There are instances of users whose security keys are not able to be enrolled as the resident key slots are filled. Multiple users describe that Android can not create Passkeys due to platform bugs. Some devices need firmware resets to create Passkeys. Keys can be saved on the client but not the server leading to duplicate account presence and credentials that don't work, or worse lead users to delete the real credentials.

The helplessness of users on these threads is obvious - and these are technical early adopters. The users we need to be advocates for changing from passwords to passkeys. If these users can't make it work how will people from other disciplines fare?

Externally there are other issues. Apple Keychain has personally wiped out all my Passkeys on three separate occasions. There are external reports we have recieved of other users who's Keychain Passkeys have been wiped just like mine.

Now as users we have the expectation that keys won't be created or they will have disappeared when we need them most.

In order to try to resolve this the workgroup seems to be doubling down on more complex JS apis to try to patch over the issues that they created in the first place. All this extra complexity comes with fragility and more bad experiences, but without resolving the core problems.

It's a mess.

The Future

At this point I think that Passkeys will fail in the hands of the general consumer population. We missed our golden chance to eliminate passwords through a desire to capture markets and promote hype.

Corporate interests have overruled good user experience once again. Just like ad-blockers, I predict that Passkeys will only be used by a small subset of the technical population, and consumers will generally reject them.

To reiterate - my partner, who is extremely intelligent, an avid computer gamer and veterinary surgeon has sworn off Passkeys because the user experience is so shit. She wants to go back to passwords.

And I'm starting to agree - a password manager gives a better experience than passkeys.

That's right. I'm here saying passwords are a better experience than passkeys. Do you know how much it pains me to write this sentence? (and yes, that means MFA with TOTP is still important for passwords that require memorisation outside of a password manager).

So do yourself a favour. Get something like bitwarden or if you like self hosting get vaultwarden. Let it generate your passwords and manage them. If you really want passkeys, put them in a password manager you control. But don't use a platform controlled passkey store, and be very careful with security keys.

And if you do want to use a security key, just use it to unlock your password manager and your email.

Within enterprise there still is a place for attested security keys where you can control the whole experience to avoid the vendor lockin parts. It still has rough edges though. Just today I found a browser that has broken attestation which is not good. You still have to dive through obnoxious UX elements that attempt to force you through caBLE even though your IDP will only accept certain security models, so you're still likely to have some confused users.

Despite all this, I will continue to maintain webauuthn-rs and it's related projects. They are still important to me even if I feel disappointed in the direction of the ecosystem.

But at this point, in Kanidm we are looking into device certificates and smartcards instead. The UI is genuinely better. Which says a lot considering the PKCS11 and PIV specifications. But at least PIV won't fall prone to attempts to enshittify it.

Read the whole story
sarcozona
5 hours ago
reply
Epiphyte City
Share this story
Delete

What's Up With That: Building Bigger Roads Actually Makes Traffic Worse | WIRED

1 Share

I grew up in Los Angeles, the city by the freeway by the sea. And if there’s one thing I’ve known ever since I could sit up in my car seat, it’s that you should expect to run into traffic at any point of the day. Yes, commute hours are the worst, but I’ve run into dead-stop bumper-to-bumper cars on the 405 at 2 a.m.

As a kid, I used to ask my parents why they couldn’t just build more lanes on the freeway. Maybe transform them all into double-decker highways with cars zooming on the upper and lower levels. Except, as it turns out, that wouldn’t work. Because if there’s anything that traffic engineers have discovered in the last few decades it’s that you can’t build your way out of congestion. It’s the roads themselves that cause traffic.

The concept is called induced demand, which is economist-speak for when increasing the supply of something (like roads) makes people want that thing even more. Though some traffic engineers made note of this phenomenon at least as early as the 1960s, it is only in recent years that social scientists have collected enough data to show how this happens pretty much every time we build new roads. These findings imply that the ways we traditionally go about trying to mitigate jams are essentially fruitless, and that we’d all be spending a lot less time in traffic if we could just be a little more rational.

But before we get to the solutions, we have to take a closer look at the problem. In 2009, two economists—Matthew Turner of the University of Toronto and Gilles Duranton of the University of Pennsylvania—decided to compare the amount of new roads and highways built in different U.S. cities between 1980 and 2000, and the total number of miles driven in those cities over the same period.

“We found that there’s this perfect one-to-one relationship,” said Turner.

If a city had increased its road capacity by 10 percent between 1980 and 1990, then the amount of driving in that city went up by 10 percent. If the amount of roads in the same city then went up by 11 percent between 1990 and 2000, the total number of miles driven also went up by 11 percent. It’s like the two figures were moving in perfect lockstep, changing at the same exact rate.

Now, correlation doesn’t mean causation. Maybe traffic engineers in U.S. cities happen to know exactly the right amount of roads to build to satisfy driving demand. But Turner and Duranton think that's unlikely. The modern interstate network mostly follows the plan originally conceived by the federal government in 1947, and it seems incredibly coincidental that road engineers at the time could have successfully predicted driving demand more than half a century in the future.

A more likely explanation, Turner and Duranton argue, is what they call the fundamental law of road congestion: New roads will create new drivers, resulting in the intensity of traffic staying the same.

Read the whole story
sarcozona
13 hours ago
reply
Epiphyte City
Share this story
Delete

Brad "Nice Bones" Dragon (@breakfastgolem@goblin.camp)

1 Share
Read the whole story
sarcozona
14 hours ago
reply
Epiphyte City
Share this story
Delete
Next Page of Stories