Putting Safety Check activation in this protective, semi-algorithmic swaddling means the company can cushion itself from blame when the feature is (or is not) activated — since it’s not making case-by-case decisions itself — yet also (apparently) sidestep the responsibility for its technology enabling widespread algorithmic stress. As is demonstrably the case here, where it’s been activated across London and beyond.
We would be much better off if we stopped accepting fake apologies and 'the algorithm did it not us' excuses.
Facebook employees programmed this thing under, I assume, the direction of management. This is Facebook's fault not some magic, wibly, wobly force. It's one thing to have a bug, but this is working as specified.
Don't forget, FB's culture is to move fast and break things. That's ok when you're breaking features, that's not acceptable when you are breaking social norms, and that's what happens when they are so damn big.
They might be sorry, but you can dry a lot of tears with wads of cash. They never see any real consequences for their mistakes.
We would be much better off if we stopped accepting fake apologies and 'the algorithm did it not us' excuses.
Facebook employees programmed this thing under, I assume, the direction of management. This is Facebook's fault not some magic, wibly, wobly force. It's one thing to have a bug, but this is working as specified.