News for hackers. Stuff that matters.
Re:996, GitHub, and China's digital workers rights awakening by sitharus on Thursday April 11, 2019 @12:18AM (#19631124)
Just tested myself and the official client refuses to send. Third-party clients are unaffected, good thing I still use one really.
Re:996, GitHub, and China's digital workers rights awakening by AFascistWorld on Thursday April 11, 2019 @02:14AM (#19631612)
Not to defend twitter, but could this be an anti-spam measure?
Re:996, GitHub, and China's digital workers rights awakening by JimDabell on Thursday April 11, 2019 @03:30AM (#19631908)
This is very unlikely because it seems to be something that happens in the official client rather than server-side. Spammers are unlikely to use official clients and blocking them there doesn't make any sense.

Having said that, if they were intentionally trying to block this then using their anti-spam mechanisms would be an obvious way of doing so, so I think it's definitely a possibility that this is some accidental side-effect of something else rather than a simple intentional block.

Re:996, GitHub, and China's digital workers rights awakening by keytarsolo on Thursday April 11, 2019 @03:54AM (#19631992)
An anti spam feature should not links typed by real humans on purpose. Lots of popular links are shared on twitter and don't get blocked via anti spam. This seems like something deliberate, even if the global part of the impact is a deployment error.