3 ms·

What scenario would justify that feature existing though? Why would they need to make posts from arbitrary accounts?

• bombcar 4y ago
  It's common in lots of software - a form of a "su" command that lets you assume all aspects of a particular user. Usually developed for testing purposes (easiest way to reproduce a problem, after all) and prevents password-sharing. But it can obviously be used for evil, and so it should be heavily logged and flagged.
  • deleted 4y ago
    [deleted]
  • ALittleLight 4y ago
    But the comment says that users wouldn't even see posts from the Twitter employee assuming their account in their own timeline. What legitimate purpose would that serve?
    • bombcar 4y ago
      I would assume some kind of "don't disturb the user while testing" but if everyone else sees them ...
      • jasonm23 4y ago
        Why would this be a production data "tool"? Makes no sense at all unless Twitter DGAF about it's users privacy... Ok, answered my own question there didn't I.
  • jasonm23 4y ago
    I worked in finance and we are brick-walled from real production data. There's obviously a way around it, but it is not a function you can pull out the company toolbox. This is a clear breach of infosec if there's a $#%*# su to post as Waldo and Waldo can't see that post. In fact it seems ONLY possible to do _evil_ with that feature.