And remember, @CDCgov already concluded in systematic review of 14 RCTs that masks don't mitigate influenza spread, and a meta analysis further evidenced that even N95 masks make no difference vs cloth masks, meaning that no masks - not even N95 - workhttps://t.co/mSwdz7U6tM
— 3PIDEMIOLOGY (@3PIDEMIOLOGY) December 31, 2020
As if they didn't know this before or conclude CONSISTENTLY after systematic review + meta analysis of randomized controlled trials that masks do not mitigate communicable viral spread?
But TRASH "health" agencies & experts continue w/their Wear A Mask campaign & suppress niacin
Bacterial Pneumonia and Other Health Risks of Wearing Masks Alarm Doctors https://t.co/8eKmIaxeMQ
— Toni (@Landau_18901) January 3, 2021
More from Health
Some thoughts on this: Firstly, it might be personal preference, but I am not keen on this kind of campaign as I feel like it trivialises cancer. Sometimes the serious message gets lost because people are sharing pics of cats or whatever and the important context is gone.
More importantly, the statistic being used in the campaign is misleading. It says 57% of women put off cervical screening if they can't get waxed. But on further investigation, that's not accurate.
The page here goes on to say "57% of women who regularly have their pubic hair professionally removed would put off attending their cervical screening appointment if they hadn’t been able to visit a beauty salon."
So the 57% represents a concern not across the whole population of women, but only those who regularly get waxed. So how big of an issue is this across the whole population? And what else is stopping people getting smears?
I think campaigns for cancer screening are really tricky because there is so much nuance that often doesn't fit into a catchy headline or hashtag. It's certainly not easy and is part of a bigger conversation.
It\u2019s #CervicalCancerPreventionWeek \U0001f499
— myGP (@myGPapp) January 18, 2021
Here\u2019s how you can help to raise awareness:
\U0001f431 Share an image of the cat that best reflects your undercarriage/flower/bits (technical term vulva!) current look.
#\u20e3Use the Hashtag #myCat.
\U0001f46dTell and tag your friends to let them know. pic.twitter.com/8aHf96ynjT
More importantly, the statistic being used in the campaign is misleading. It says 57% of women put off cervical screening if they can't get waxed. But on further investigation, that's not accurate.
The page here goes on to say "57% of women who regularly have their pubic hair professionally removed would put off attending their cervical screening appointment if they hadn’t been able to visit a beauty salon."
So the 57% represents a concern not across the whole population of women, but only those who regularly get waxed. So how big of an issue is this across the whole population? And what else is stopping people getting smears?
I think campaigns for cancer screening are really tricky because there is so much nuance that often doesn't fit into a catchy headline or hashtag. It's certainly not easy and is part of a bigger conversation.
You May Also Like
A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.