Facebook made mistakes, says Zuckerberg; vows to 'fix'

Agencies
March 22, 2018

Washington, Mar 22: In the midst of revelations of a major data breach, Facebook CEO Mark Zuckerberg today admitted that his company made mistakes on user data secrecy and vowed to take steps to prevent the misuse or breach of personal data of users by developers or business partners.

Zuckerberg, 33, through a lengthy Facebook post, broke his silence over the alleged privacy scandal that hit the social media giant.

"I started Facebook, and at the end of the day, I'm responsible for what happens on our platform. I'm serious about doing what it takes to protect our community," Zuckerberg said.

Reports alleged that personal data from as many as 50 million people might have been used improperly in Donald Trump's 2016 presidential campaign by Cambridge Analytica, a UK-based political research firm.

Zuckerberg said Facebook has a "responsibility" to protect its users' data and if it fails, "we don't deserve to serve you."

He acknowledged that there is more the company needs to do.

"...But we also made mistakes, there's more to do, and we need to step up and do it," he said.

Over the past several days, Facebook has been facing an investigation by the Federal Trade Commission and calls for legislative testimonies in the US and Europe.

India's IT and Law Minister Ravi Shankar Prasad has warned social media companies such as Facebook of stringent actions if there was an attempt to influence the electoral process of any country.

Amidst a global outrage against Facebook, the Silicon Valley-based company, which currently has 2 billion monthly active users, has suffered a loss of USD 50 billion in market value.

In a damage control mode, Zuckerberg announced a slew of measures aimed to "secure our platform further and make our community safer for everyone going forward".

For this, the Facebook founder said, his company will take three steps to prevent the data misuse.

"We will investigate all apps that had access to large amounts of information before we changed our platform to dramatically reduce data access in 2014, and we will conduct a full audit of any app with suspicious activity," he said.

"We will ban any developer from our platform that does not agree to a thorough audit. And if we find developers that misused personally identifiable information, we will ban them and tell everyone affected by those apps," he added.

Zuckerberg said that the second step is to restrict developers' data access even further to prevent other kinds of abuse.

He cited an example for this: "It (Facebook) will remove developers' access to one's data if the app hasn't been used by the person in three months."

"We will reduce the data you give an app when you sign in -- to only your name, profile photo, and email address. We'll require developers to not only get approval but also sign a contract in order to ask anyone for access to their posts or other private data. And we'll have more changes to share in the next few days," Zuckerberg said.

In the last of the three steps, he said in the next month Facebook will show everyone a tool at the top of their News Feed with the apps they have used and an easy way to revoke those apps' permissions to their data.

"We already have a tool to do this in your privacy settings, and now we will put this tool at the top of your News Feed to make sure everyone sees it, Zuckerberg said.

Zuckerberg said that his company had already taken a series of steps in 2014.

Giving a timeline of the events, Zuckerberg said in 2013, a Cambridge University researcher named Aleksandr Kogan created a personality quiz app. It was installed by around 300,000 people who shared their data as well as some of their friends' data.

Given the way Facebook platform worked at the time, this meant Kogan was able to access tens of millions of their friends' data, he said.

Zuckerberg said in order to prevent the "abusive apps", a series of measures were taken in 2014 to dramatically limit the data apps could access.

In 2015, Facebook learned from journalists at The Guardian that Kogan had shared data from his app with Cambridge Analytica. It is against Facebook's policies for developers to share data without people's consent, he said, adding that he immediately banned Kogan's app from Facebook, and demanded that Kogan and Cambridge Analytica formally certify that they had deleted all improperly acquired data. They provided these certifications.

Zuckerberg cited some media reports that suggested Cambridge may not have deleted the data as they had certified.

This, according to him, was not only a breach of trust between Kogan, Cambridge and Facebook but also between his company and its users.

"But it was also a breach of trust between Facebook and the people who share their data with us and expect us to protect it. We need to fix that," he said.

"In this case, we already took the most important steps a few years ago in 2014 to prevent bad actors from accessing people's information in this way. But there's more we need to do," Zuckerberg said.

Comments

Add new comment

  • Coastaldigest.com reserves the right to delete or block any comments.
  • Coastaldigset.com is not responsible for its readers’ comments.
  • Comments that are abusive, incendiary or irrelevant are strictly prohibited.
  • Please use a genuine email ID and provide your name to avoid reject.
News Network
December 6,2025

pilot.jpg

New Delhi: IndiGo, India’s largest airline, faced major operational turbulence this week after failing to prepare for new pilot-fatigue regulations issued by the Directorate General of Civil Aviation (DGCA). The stricter rules—designed to improve flight safety—took effect in phases through 2024, with the latest implementation on November 1. IndiGo has acknowledged that inadequate roster planning led to widespread cancellations and delays.

Below are the key DGCA rules that affected IndiGo’s operations:

1. Longer Mandatory Weekly Rest

Weekly rest for pilots has been increased from 36 hours to 48 hours.

The government says the extended break is essential to curb cumulative fatigue. This rule remains in force despite the current crisis.

2. Cap on Night Landings

Pilots can now perform only two night landings per week—a steep reduction from the earlier limit of six.

Night hours, defined as midnight to early morning, are considered the least alert period for pilots.

Given the disruptions, this rule has been temporarily relaxed for IndiGo until February 10.

3. Reduced Maximum Night Flight Duty

Flight duty that stretches into the night is now capped at 10 hours.

This measure has also been kept on hold for IndiGo until February 10 to stabilize operations.

4. Weekly Rest Cannot Be Replaced With Personal Leave

Airlines can no longer count a pilot’s personal leave as part of the mandatory 48-hour rest.

Pilots say this closes a loophole that previously reduced actual rest time.

Currently, all airlines are exempt from this rule to normalise travel.

5. Mandatory Fatigue Monitoring

Airlines must submit quarterly fatigue reports along with corrective actions to DGCA.

This system aims to create a transparent fatigue-tracking framework across the industry.

The DGCA has stressed that these rules were crafted to strengthen flight safety and align India with global fatigue-management standards. The temporary relaxations are expected to remain until February 2025, giving IndiGo time to stabilise its schedules and restore normal air travel.

Comments

Add new comment

  • Coastaldigest.com reserves the right to delete or block any comments.
  • Coastaldigset.com is not responsible for its readers’ comments.
  • Comments that are abusive, incendiary or irrelevant are strictly prohibited.
  • Please use a genuine email ID and provide your name to avoid reject.
News Network
December 4,2025

indigoflight.jpg

Domestic carrier IndiGo has cancelled over 180 flights from three major airports — Mumbai, Delhi and Bengaluru — on Thursday, December 4, as the airline struggles to secure the required crew to operate its flights in the wake of new flight-duty and rest-period norms for pilots.

While the number of cancellations at Mumbai airport stands at 86 (41 arrivals and 45 departures) for the day, at Bengaluru, 73 flights have been cancelled, including 41 arrivals, according to a PTI report that quoted sources.

"IndiGo cancelled over 180 flights on Thursday at three airports-Mumbai, Delhi and Bengaluru," the source told the news agency.

Besides, it had cancelled as many as 33 flights at Delhi airport for Thursday, the source said, adding, "The number of cancellations is expected to be higher by the end of the day."

The Gurugram-based airline's On-Time Performance (OTP) nosedived to 19.7 per cent at six key airports — Delhi, Mumbai, Chennai, Kolkata, Bengaluru and Hyderabad — on December 3, as it struggled to get the required crew to operate its services, down from almost half of December 2, when it was 35 per cent.

"IndiGo has been facing acute crew shortage since the implementation of the second phase of the FDTL (Flight Duty Time Limitations) norms, leading to cancellations and huge delays in its operations across the airports," a source had told PTI on Wednesday.

Chaos continued at several major airports for the third day on Thursday because of the cancellations.

A spokesperson for the Kempegowda International Airport (KIA) in Bengaluru said that 73 IndiGo flights had been cancelled on Thursday.

At least 150 flights were cancelled and dozens of others delayed on Wednesday, airport sources said, leaving thousands of travellers stranded, according to news agency Reuters.

The Directorate General of Civil Aviation (DGCA) has said it is investigating IndiGo flight disruptions and has asked the airline to submit the reasons for the current situation, as well as its plans to reduce flight cancellations and delays.

It may be mentioned here that the pilots' body, Federation of Indian Pilots (FIP), has alleged that IndiGo, despite getting a two-year preparatory window before the full implementation of new flight duty and rest period norms for cockpit crew, "inexplicably" adopted a "hiring freeze".

The FIP said it has urged the safety regulator, the DGCA, not to approve airlines' seasonal flight schedules unless they have adequate staff to operate their services "safely and reliably" in accordance with the New Flight Duty Time Limitations (FDTL) norms.

In a letter to the DGCA late on Wednesday, the FIP urged the DGCA to consider re-evaluating and reallocating slots to other airlines, which have the capacity to operate them without disruption during the peak holiday and fog season if IndiGo continues to "fail in delivering on its commitments to passengers due to its own avoidable staffing shortages."

Comments

Add new comment

  • Coastaldigest.com reserves the right to delete or block any comments.
  • Coastaldigset.com is not responsible for its readers’ comments.
  • Comments that are abusive, incendiary or irrelevant are strictly prohibited.
  • Please use a genuine email ID and provide your name to avoid reject.
News Network
December 4,2025

Mangaluru: Chaos erupted at Mangaluru International Airport (MIA) after IndiGo flight 6E 5150, bound for Mumbai, was repeatedly delayed and ultimately cancelled, leaving around 100 passengers stranded overnight. The incident highlights the ongoing country-wide operational disruptions affecting the airline, largely due to the implementation of new Flight Duty Time Limitations (FDTL) norms for crew.

The flight was initially scheduled for 9:25 PM on Tuesday but was first postponed to 11:40 PM, then midnight, before being cancelled around 3:00 AM. Passengers expressed frustration over last-minute communication and the lack of clarity, with elderly and ailing travellers particularly affected. “Though the airline arranged food, there was no proper communication, leaving us confused,” said one family member.

An IndiGo executive at MIA cited the FDTL rules, designed to prevent pilot fatigue by limiting crew working hours, as the cause of the cancellation. While alternative arrangements, including hotel stays, were offered, about 100 passengers chose to remain at the airport, creating tension. A replacement flight was arranged but also faced delays due to the same constraints, finally departing for Mumbai around 1:45 PM on Wednesday. Passengers either flew, requested refunds, or postponed their travel.

The Mangaluru delay is part of a broader crisis for IndiGo. The airline has been forced to make “calibrated schedule adjustments”—a euphemism for widespread cancellations and delays—after stricter FDTL norms came into effect on November 1.

While an IndiGo spokesperson acknowledged unavoidable flight disruptions due to technology issues, operational requirements, and the updated crew rostering rules, the DGCA has intervened, summoning senior airline officials to explain the chaos and outline corrective measures.

The ripple effect has been felt across the country, with major hubs like Bengaluru and Mumbai reporting numerous cancellations. The Mangaluru incident underscores the systemic operational strain currently confronting India’s largest carrier, leaving passengers nationwide grappling with uncertainty and delays.

Comments

Add new comment

  • Coastaldigest.com reserves the right to delete or block any comments.
  • Coastaldigset.com is not responsible for its readers’ comments.
  • Comments that are abusive, incendiary or irrelevant are strictly prohibited.
  • Please use a genuine email ID and provide your name to avoid reject.