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
    42•2 years ago

    Didn’t even know they had it

    Can they add Lemmy-style threaded replies? It’s dumb that thread depth is fixed at 1. We had infinitely threaded replies way back in the BBS days, it isn’t exactly a new feature.

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

      Which BBS systems did you use? The ones I used (which mostly ran Renegade) didn’t have branching threads; we’d just quote whichever message we were replying to.

    • @[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.

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

      I don’t know if deeper thread branching is a good idea. I’m already struggling to find Slack comments from people who are in multiple channels and DMs each with various threads off of a main comment

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

      They only added threading because teams added it. I hated it when it launched. Now I find it kinda useful, but if they were deeply nested things would undoubtedly get lost. Either way I don’t think it’s a technical limitations so much as it’s a product design choice.