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.

  • @Bye@lemmy.worldEnglish
    41•1 year 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.

    • @hperrin@lemmy.worldEnglish
      22•1 year 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.

        • @hperrin@lemmy.worldEnglish
          17•1 year 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.

    • @lenny@r.nfEnglish
      12•1 year 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.

    • @PizzasDontWearCapes@sh.itjust.worksEnglish
      6•1 year 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

    • @WhiskyTangoFoxtrot@lemmy.worldEnglish
      3•1 year 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.