A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::open($save_path, $name) should either be compatible with SessionHandlerInterface::open(string $path, string $name): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 6

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::close() should either be compatible with SessionHandlerInterface::close(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 7

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::read($session_id) should either be compatible with SessionHandlerInterface::read(string $id): string|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 8

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::write($session_id, $session_data) should either be compatible with SessionHandlerInterface::write(string $id, string $data): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 9

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::destroy($session_id) should either be compatible with SessionHandlerInterface::destroy(string $id): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 10

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::gc($maxlifetime) should either be compatible with SessionHandlerInterface::gc(int $max_lifetime): int|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 11

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 284

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_set_cookie_params(): Session cookie parameters cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 291

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 306

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 316

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 317

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 318

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 319

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 377

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_set_save_handler(): Session save handler cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 110

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_start(): Session cannot be started after headers have already been sent

Filename: Session/Session.php

Line Number: 143

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

NRIPage | Articles | Gaurav Kapoor Mocks Ranveer Allahbadia’s Quick Apology Amid Controversy Over Offensive Joke | Get Fashion & Beauty Ideas. Elevate Your Style and Confidence - NRI Page
Edit

Gaurav Kapoor Mocks Ranveer Allahbadia’s Quick Apology Amid Controversy Over Offensive Joke

Gaurav Kapoor Mocks Ranveer Allahbadia’s Quick Apology Amid Controversy Over Offensive Joke

Gaurav Kapoor Mocks Ranveer Allahbadia’s Quick Apology Amid Controversy

YouTuber and podcaster Ranveer Allahbadia is facing backlash over an insensitive joke about parental sex on the show India’s Got Latent. The remark sparked public outrage, leading to a police case against him, comedian Samay Raina, and the show’s producers and judges.

In response to the controversy, Ranveer issued a public apology just two hours after the backlash began—a move that comedian Gaurav Kapoor hilariously roasted in his latest stand-up act.


Gaurav Kapoor’s Take on Ranveer’s Fast Apology

Gaurav Kapoor, known for his sharp wit, joked about how quickly Ranveer apologized, making fun of the speed at which he tried to fix the situation.

"Arre bhai, kya bhasad ho gayi yaar. Itni badi bhasad toh hai bhi nahi yaar. Ho gaya yaar, nikal gaya mooh se yaar."
(It became such a big mess when it wasn't even that big. It’s fine, they messed up.)

He then poked fun at how Ranveer apologized within just two hours, comparing it to how long it takes for someone to apologize to their parents:

"Mujhe gire pe laat marna accha nahi lagta par ek baar maar dete hain. Waise Ranveer jo bhai hain, 12 baje controversy hui, 2 baje apology dedi. 2 ghante mein? Itni jaldi toh main apne papa ko sorry nahi bolta!"
(I don’t like to kick someone when they’re down, but let’s do it once. The controversy started at 12, and Ranveer apologized at 2. In just 2 hours? I don’t even apologize to my dad that fast!)

“Should Have Consulted a Lawyer First”

Kapoor then mocked Ranveer for not consulting a lawyer before apologizing, hinting that his premature response may have worsened the situation.

"Abe ruk ja bhootni ke, lawyer ko de de thoda paisa. Baat karle lawyer se, samajh le kya bolna hai."
(Wait a minute! Pay a lawyer and consult them first. Understand what you need to say.)


A Satirical Historical Comparison

Kapoor took the joke further, comparing Ranveer’s fast submission to how someone would react under British rule before India’s independence:

"Agar ye 1947 se pehle paida hota na, angrezo ke saath mil jaata. Ek danda padte hi, ‘Simon bhai sorry! Main aapke saath chal raha hoon, Simon bhai’."
(If he had been born before 1947, he would have joined the British. One hit with a stick, and he’d be like, ‘Brother Simon, sorry! I’m with you, Brother Simon.’)


The Fallout from the Controversy

Ranveer Allahbadia, Samay Raina, and the team behind India’s Got Latent are now facing legal trouble, with police complaints filed for obscene and offensive remarks made on the show.

While Ranveer may have hoped to control the damage with his quick apology, Kapoor’s stand-up routine suggests that a well-planned response—perhaps after consulting legal counsel—might have been the smarter move.

With controversy brewing, it remains to be seen how the legal battle unfolds and whether Ranveer’s apology will help or worsen the situation.

What is your response?

joyful Joyful 0%
cool Cool 0%
thrilled Thrilled 0%
upset Upset 0%
unhappy Unhappy 0%
AD
AD