When Biodun Fatoyinbo's case went viral, Timi Adigun of Mine Teenage Ministry told his church members not to be talebearers or speak against a man of God.
Little did anyone know that he himself had been sexually abusing and harassing his female teenage members for years!
Yes, maybe it is untrue but he and his wife suddenly shut down their church, The Ark, when news broke out. It may not be true but they cancelled all events till further notice.
May not be true but he has started another church lowkey in another name
May not be true but members are getting encouraged not to be "talebearers".
But he has refused to say NADA. He is even running giveaways on IG.
But well, they're talking about love on IG.
Jesus, you need to come back ASAP.
https://t.co/P0ANlTJQic
No need to go too far, Orifunke. I was the head of the Ilorin arm of the ministry(you can check any MINE Magazine publication around that time for my name) in 2014 and 2015 and joined the ministry in 2011.
— BRAVEDAVE \u270d\U0001f3fe\U0001f5e3\ufe0f (@The_bravedave) December 10, 2020
I've listened to voice notes where he admitted all these things. https://t.co/Lq2nUR2roK
More from For later read
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.