4 ms·

That's a really short window to salvage your data.

• meitros 5y ago
  This happened with another Twitter acquisition Smyte, where in that case they shut down the api immediately [1]. It seems like it’s some property of Twitter’s acquisition process? [1] https://techcrunch.com/2018/06/21/twitter-smytes-customers/amp/ https://techcrunch.com/2018/06/21/twitter-smytes-customers/a...
  • esjeon 5y ago
    So the Twitter lead engineer said "We're gonna learn from this". So they gone from 15 minutes (Smyte) to 4 days (Quill) - a 38400% improvement. /s
  • breakingcups 5y ago
    Apparently also happened with an app called Squad, exactly a year ago. https://twitter.com/squad/status/1337398991210725379 https://twitter.com/squad/status/1337398991210725379
  • atdrummond 5y ago
    I feel bad whenever I read about this because I’m friends with a Smyte founder and I know they absolutely didn’t want things to play out the way they did. I had hoped Twitter learned their lesson.
  • Alex3917 5y ago
    > It seems like it’s some property of Twitter’s acquisition process? What if there are serious security vulnerabilities though? I could see having a process where founders don't turn over their source code until midnight when the deal closes, and then the acquiring company gets the option to shut it down immediately if there are serious and unfixable security vulnerabilities discovered between midnight and 10am when the press release goes out. I'm not saying this hypothetical process is a good one, much less that this is what happened, but I could certainly imagine things playing out this way.