Urgent.News

What's breaking now, across thousands of outlets.

Tech

Meta akui kesilapan teknikal antara punca akaun WhatsApp pengguna sah digantung

SKMM berkata kesilapan itu dikenal pasti dalam lebih separuh kes bagi kumpulan pertama yang dirujuk kepada syarikat teknologi berkenaan.

Meta akui kesilapan teknikal antara punca akaun WhatsApp pengguna sah digantung

Meta has acknowledged a technical error in its system that incorrectly identified legitimate WhatsApp user activity as rule violations, impacting over half of the cases submitted by the Malaysian Communications and Multimedia Commission (MCMC). In a statement, MCMC shared that they received feedback from Meta on the issue and confirmed that the technical error was fixed towards the end of September.

The error had led to the wrongful suspension of legitimate accounts, including some that hadn't submitted an appeal. Meta assured that no changes were made to its enforcement policies or WhatsApp Terms of Service. MCMC elaborated that the suspensions could be due to various factors such as recycled phone numbers linked to blocked accounts, spam or scam activity, and usage patterns detected by WhatsApp's security systems.

User reports are also considered but not the only basis for account suspension. For business accounts, Meta stated that sending messages without consent or in high volumes, especially to non-contact recipients, could be flagged as spam activity. MCMC is urging Meta to enhance its appeal and recovery processes, requesting confirmation, status updates, and faster action for affected users.

They advised users to utilize WhatsApp's official appeal and support channels. MCMC reiterated that they will keep monitoring the resolution of outstanding cases and will consider further regulatory action if Meta's measures prove inadequate.

Written by urgent.news from Malay Mail's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

This story

This is one outlet's version. Read the fullest account.

Read the original at freemalaysiatoday.com →

More in Tech

Why a missing JavaScript file can stay missing after you deploy it

I built cachewhy around a small but costly HTTP cache mistake. Imagine a request for /missing.js that returns 404 with Cache-Control: public, max-age=2678400 . That lifetime is 31 days.

  • Missing JavaScript file persists due to long-lived HTTP cache.
  • Browser stores 404 response in private and shared caches.
  • Cachewhy tool reveals cache details and caching behavior.

I built CompressGIF: local GIF compression, plus REST and MCP APIs

A GIF can be useful in a README, bug report, or product demo—and still be too large to attach. Getting it below an upload limit often means trying compression settings, checking the animation, and…

  • CompressGIF tool compresses GIF files for documentation and demos
  • Browser compressor offers quality, size, or size-target modes
  • REST API provides asynchronous compression service for developers

More from Saturday 3 October →