The six-day compliance window, with directives issued November 24 and effective November 30, is remarkably short for platform-level changes at Apple and Google's scale, and that both companies apparently complied within it suggests these controls were technically ready but needed a regulatory trigger. The underlying problem remains: users treat iMessage and Google Messages as authenticated channels when they are not, and the fix reduces visual prominence of spoofed sender names rather than authenticating sender identity. The SMS Sender ID Registry that protects the gov.sg identifier on traditional SMS has no equivalent in these OTT messaging environments.
The six-day compliance window, with directives issued November 24 and effective November 30, is remarkably short for platform-level changes at Apple and Google's scale, and that both companies apparently complied within it suggests these controls were technically ready but needed a regulatory trigger. The underlying problem remains: users treat iMessage and Google Messages as authenticated channels when they are not, and the fix reduces visual prominence of spoofed sender names rather than authenticating sender identity. The SMS Sender ID Registry that protects the gov.sg identifier on traditional SMS has no equivalent in these OTT messaging environments.