3 ms·
This wouldn't have fallen within "trust and safety" purview. This should've been caught in even the most cursory of code reviews.
by ceejayoz 3y ago
This wouldn't have fallen within "trust and safety" purview. This should've been caught in even the most cursory of code reviews.
- somenameforme 3y agoIt seems this may have only affected the X on iOS App. [1] That greatly expands the range of possible causes. It also makes this quite odd in another way as well, because it suggests this was not a server side change. [1] - https://news.ycombinator.com/item?id=39991312 https://news.ycombinator.com/item?id=39991312
- sangnoir 3y agoWhy wouldn't phishing fall under trust and safety? Perhaps not primarily - but it's definitely a trust and safety event.
- ceejayoz 3y agoThey wouldn't "have been the ones to flag something like this down". It should've been caught long prior; the code shouldn't have been written, it shouldn't have survived code review, and it should've failed automated tests. It's a trust and safety incident now, but it never should have been.
- blasphemers 3y agoThe trust and safety team was only responsible for censoring wrongthink