#MeToo: Jami tweets more details of his 'rape' ordeal

Film-maker vows to never give up regardless of the pressure or how the story is presented


Entertainment Desk October 23, 2019
PHOTO: EXPRESS TRIBUNE

Monday morning saw the internet go through a meltdown when renowned film-maker Jami shared his #MeToo story on Twitter.

The director shared horrifying details of how he was raped 13 years ago and the trauma that followed.



Social media users and celebrities at large came in support of the Moor director, appreciating him for having the courage to share his ordeal on a public platform and starting a conversation about men as survivors and victims of rape.

The director expressed his gratitude for all the support he received and remained positive about the consequences of the #MeToo movement.



That, however, did not stop him from tweeting specific details of his #MeToo story.

On Wednesday morning, he took to Twitter to respond to the people referred to as ‘they’, who will supposedly push him around for his confession and why that won’t force him to give in to the pressure.

TRIGGER WARNING!



“It’s simple if they push me around which he [accused] can easily then he should know that I have nothing to lose now,” Jami wrote. “I will spill moment by moment details of that day [of the incident]. From the lunch with his mother to doping to brutal details of his ring cutting me from the inside and his elbow pushed hard on my neck.”

Jami further said that he would not give up regardless of how the story is presented, that he ‘enjoyed it’ or something else. “To keep saying afterwards to admit that I enjoyed it, to sitting in my car screaming crying in middle of Marriott road and other details which are etched on my DNA now. I don’t give up remember that. I never give up! Had enough!” the director concluded.

Have something to add to the story? Please share it in the comments below

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ