Meta Localhost Tracking Controversy and the Rose v Meta Lawsuit
Meta has ceased localhost tracking on Android
Meta has stopped using the Facebook Pixel to send packets or requests to localhost on Android devices. According to reports from localmess.github.io, the code responsible for sending the _fbp cookie via localhost was almost entirely removed as of June 3rd. Yandex was also noted to have stopped this specific practice.
Legal ramifications: Rose v Meta
Meta is facing a class-action lawsuit, Rose v Meta, alleging the company secretly tracked Android users' browsing activity. The lawsuit claims that between September 2024 and June 2025, Meta exploited Android's localhost—a feature intended for software developers to test applications—to connect mobile web browsing activity to Facebook and Instagram profiles.
U.S. District Court Judge Rita Lin in San Francisco ruled that the case could proceed. The litigation has evolved to include Google as a defendant in consolidated privacy cases, with motions to dismiss from both Meta and Google having been denied.
Browser-level mitigations and Local Network Access (LNA)
To prevent unauthorized local network exploitation, Chrome and Firefox are deploying "Local Network Access" (LNA) protections. This security feature prompts the user when an application attempts to access the local network, preventing silent tracking via localhost.
Technical challenges remain for legitimate local network use cases. For instance, developers attempting to access LAN services (such as WebDAV servers) via service.local often face blocks on fetch/XHR requests due to mixed content rules, even with CORS configured, because .local domains cannot obtain SSL certificates. While Chrome's LNA allows these requests if the user grants permission, they still trigger mixed content warnings in the console.
Community Perspectives on Engineering Ethics
The controversy surrounding the implementation of tracking features has sparked discussion regarding the role of professional associations in software engineering. One community member suggested that a software engineer's union could provide a mechanism for developers to refuse the implementation of unethical features by citing union rules as a justification for non-compliance.
"i would love to have a software engineer's union, not so much to get better working conditions but to be able to say stuff like 'i can't implement that unethical feature, it's against union rules and i'd lose my membership'."