THREAD PART 1.
On Sunday 21st June, 14 year old Noah Donohoe left his home to meet his friends at Cave Hill Belfast to study for school. #RememberMyNoah💙


https://t.co/SyJ38zRKdG




"https://t.co/DdjhIQhC3P
https://t.co/3xddfKIcOi

I can say for a FACT he ran exhausted to the top of that dead end street naked..that is 3evidence in it self
— FIONA DONOHOE (@FIONADONOHOE2) October 24, 2020

https://t.co/qSSQ4taHit
The bins, on the tuesday ,2 days after Noah was reported missing, where allowed to be emptied as police stood on street
— FIONA DONOHOE (@FIONADONOHOE2) October 14, 2020
That tuesday, same day bins were emptied..I went to that street and they didn't allow me up to that search area to look for myself..I may have pointed out the storm drain as the elephant in the room!!
— FIONA DONOHOE (@FIONADONOHOE2) October 14, 2020
The public are upset that the police were suggesting "No foul play" before an autopsy had ever taken place with Noah after the discovery of his body, 950m inside a storm drain, in an area he was completely unfamiliar with https://t.co/dSAAXGDO4m

https://t.co/zkLB63hBC2
More from Crime
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.