Algorithmic Sabotage Work -

If you are researching this topic for a specific project, please let me know:

Constant tracking of location, speed, or active time.

Algorithms frequently punish workers automatically—through automated shift cuts or algorithmic firing—without offering a human channel for context or appeal. algorithmic sabotage work

Amazon now uses "distance likelihood scores" to detect if a picker is taking an inefficient route. Uber has begun cross-referencing GPS drift with accelerometer data (bumps in the road) to verify if a driver is actually moving or just sitting with the engine on.

This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later. If you are researching this topic for a

Other drivers use physical decoys, such as hanging multiple phones in trees near delivery hubs to trick GPS systems into thinking a driver is closer to a restaurant than they actually are, securing a competitive advantage for orders. 2. Warehousing and Logistics Slowdowns

We may also see the rise of "sabotage-as-a-service." Imagine a mobile app that sits between you and your employer's tracking software, automatically inserting random, biologically plausible micro-pauses to defeat keystroke logging, or subtly shifting your GPS coordinates to avoid punitive geofencing. (Note: Several such apps already exist in the Chinese labor market; they are called "anti-996 tools.") If you share with third parties, their policies apply

But as algorithmic management has tightened its grip, workers have found a way to push back. Enter What is Algorithmic Sabotage?

Platforms will continue to tighten their algorithmic controls, investing in more sophisticated detection systems and legal enforcement. But each tightening is likely to produce new forms of resistance. As the "Red Queen" model predicts, this co-evolutionary dynamic may be —a permanent feature of the algorithmic workplace, not a temporary bug.