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.

  • TheFunkyMonk@lemmy.worldEnglish
    2091·
    1 year ago

    I still haven’t had to update a Twitter logo on a website yet. We’ve had it come up for 3 clients so far, and they’ve all just decided to drop it. You love to see it.

    • ayyndrew@lemm.eeEnglish
      65·
      1 year ago

      I saw the X logo on a Bundesliga broadcast for the first time and it looks so out of place

  • Tygr@lemmy.worldEnglish
    122·
    1 year ago

    As a developer, I’ve only had people request removal of Twitter. They’d rather lose the bird than add an X.

  • lemmyvore@feddit.nlEnglish
    964·
    1 year ago

    I thought this was about Slackware ditching X11 for a moment… which, arguably, would have been a more interesting piece of tech news.

  • Bye@lemmy.worldEnglish
    431·
    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
      3310·
      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
          213·
          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.

  • AutoTL;DR@lemmings.worldBEnglish
    19·
    1 year ago

    This is the best summary I could come up with:

    Slack has retired its integration with X (formerly Twitter) because of X’s API changes introduced earlier this year.

    According to Slack, X’s API changes affected the functionality of the integration, which led to the decision to retire it.

    “Slack’s integration with X relies on access to its API, and changes to that API this spring impacted the integration’s functionality and the services it supports,” Rod Garcia, Slack’s VP of software engineering, said in a statement to The Verge.

    The retirement means that Slack’s X integration is just one of many useful things relying on X / Twitter data that has gone away because of the changes instituted under Elon Musk’s ownership.

    In January, X banned third-party apps, which my former colleague Mitchell Clark argued made the site what it is today.

    When asked for comment, X’s press email replied with its recent standard auto-reply: “Busy now, please check back later.”

    The original article contains 260 words, the summary contains 149 words. Saved 43%. I’m a bot and I’m open source!