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!

Timi Adigun runs a teenage ministry whose MAJOR core value is sexual purity. They run a yearly VIRGINITY day. If anyone should be caught in such a scandal, it should NOT be Timi Adigun. Not him.
"Oh, maybe it is not true".

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
It may not be true but comments are restricted on IG and people are getting blocked for asking questions.

May not be true but members are getting encouraged not to be "talebearers".
If you know anyone who was actively a member of the teenage ministry (whether teenagers or adults), please check in with them. I have spoken with a number of them in the last two months and those people are extremely hurt and broken. Too hurt.
The interesting thing is the members are only asking him to come out and address it. They want him to admit it, justice to be followed after and healing gotten for victims. That's what they are asking.

But he has refused to say NADA. He is even running giveaways on IG.
Oh, and his wife. The loving, meek, motherly Aunty Titi. His wife is also COMPLICIT. Knows about everything.

But well, they're talking about love on IG.

Jesus, you need to come back ASAP.
If you need more: https://t.co/FnLLUbFRtp
Ask any MINE Ministry member and they would affirm it. Including their ex-pastors. There was a form created by @theakanimoh and a team of investigative journalists to get victims to speak too. Go through that link I posted in my last thread and see former members affirming.
Interesting there are voice notes.
https://t.co/P0ANlTJQic

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.