So far this year, we’ve taken three closed churches into our care. They were no longer needed for worship. Two would have been demolished.

Our places of worship are the spiritual investment of generations, and they should survive.

The churches we’ve saved in 2020 are… 
#thread

St Helen's, Barmby-on-the-Marsh, Yorkshire closed in 2007. The earliest record of a chapel here dates to 1388. In 1489, the parishioners petitioned at Rome for a grander church. This was granted. Only the nave survives from this date.

2/
The medieval tower with timber spire was ruinous by 1773, and was dismantled, rebuilt in red brick and crowned with a copper cupola. The chancel seems to have been added only in the 19th century, when the church was restored in 1854 by Thomas Clarke.

3/
We are undertaking repairs now – with financial assistance from the Culture Recovery Fund.

We are delighted that we could save this church from the wrecking ball.

4/
Like St Helen’s, St Lawrence’s, Hutton Bonville, NR of Yorkshire also closed in 2007. It has lain empty since then. St Lawrence’s is a small medieval church that was much altered in the 18th and 19th centuries.

5/
There’s a lot of work to be done before we can open this church to visitors. From next spring, we will address the structural issues, restore the interior and welcome people back inside after many, many years.

6/
Buried in the churchyard is the Hon. Charles Stewart Rolls, pioneer aviator, who died 1910 in a flying accident, the first British aircraft fatality. It was C. S. Rolls that co-founded the Rolls-Royce firm.

8/
Repairs are needed to all three of these churches, but we are optimistic that we will be able welcome people back into these important buildings next summer. 

9/
We work on a shoestring. We put everything we can into saving, repairing, and opening up places of worship. It’s your membership and donations that enables us to do this – so, thank you! *You* saved these churches!

For more info on all 3 churches: https://t.co/xctVxbyy85 

10/

You May Also Like

Recently, the @CNIL issued a decision regarding the GDPR compliance of an unknown French adtech company named "Vectaury". It may seem like small fry, but the decision has potential wide-ranging impacts for Google, the IAB framework, and today's adtech. It's thread time! 👇

It's all in French, but if you're up for it you can read:
• Their blog post (lacks the most interesting details):
https://t.co/PHkDcOT1hy
• Their high-level legal decision: https://t.co/hwpiEvjodt
• The full notification: https://t.co/QQB7rfynha

I've read it so you needn't!

Vectaury was collecting geolocation data in order to create profiles (eg. people who often go to this or that type of shop) so as to power ad targeting. They operate through embedded SDKs and ad bidding, making them invisible to users.

The @CNIL notes that profiling based off of geolocation presents particular risks since it reveals people's movements and habits. As risky, the processing requires consent — this will be the heart of their assessment.

Interesting point: they justify the decision in part because of how many people COULD be targeted in this way (rather than how many have — though they note that too). Because it's on a phone, and many have phones, it is considered large-scale processing no matter what.
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.