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.

  • Spectacle8011A
    link
    fedilink
    arrow-up
    49
    arrow-down
    1
    ·
    1 year ago

    For a moment, I thought this meant Slack was now only going to work on Wayland compositors…

  • switches@kbin.social
    link
    fedilink
    arrow-up
    22
    ·
    1 year ago

    doesn’t shock me. it feels like everything on twitter is broke these days, way easier to just not deal with it.

  • AutoTL;DR@lemmings.worldB
    link
    fedilink
    English
    arrow-up
    9
    ·
    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!

  • DrQuint@lemm.ee
    link
    fedilink
    arrow-up
    9
    ·
    edit-2
    1 year ago

    The majority of companies who use Slack (over the likes of Teams) are tech-oriented companies made mid last decade.

    Making a Twitter scrapper that pushes to a webhook would take half a day and would cost essentially zero if you just toss it in a random cloud cluster and forget about it. And if you don’t have that scale, then you likely have a team leader somewhere who will run it on a machine of their own out of spite.

    And scrappers are way more wasteful for the target webhost.

    This change hurts literally nobody other than Felon. Good.