X’s API changes are to blame.

Slack gets rid of its X integration::Slack has retired its integration with X (formerly Twitter) because of X’s API changes introduced earlier this year. It’s just one of many useful apps that used Twitter’s data that’s now gone.

  • @[email protected]English
    33•2 years ago

    But it’s really hard to add one new database column that’s just a single foreign key. That would take, like, a few minutes of work.

    • @[email protected]English
      39•2 years ago

      And then index it, provision appropriate storage at the appropriate speed for it, decide how to shard it, update stored procedures to be aware of it, update the API to include it where necessary, update the clients to use it and render it correctly in the GUI, and give a heads up to integration developers of the likely breaking change.

      Yeah, few minutes, tops.

      • @[email protected]English
        21•2 years ago

        Most of that is already done, or is trivial considering they already support nested conversations with a depth of 1.

        I can guarantee you this is not a technical decision, this is a UX decision.