Slack gets rid of its X integration
Slack gets rid of its X integration
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.
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.
I saw the X logo on a Bundesliga broadcast for the first time and it looks so out of place
I don't blame them, it's a bit like having a swastika on your website.
As a developer, I’ve only had people request removal of Twitter. They’d rather lose the bird than add an X.
A bird in the hand is worth….very little apparently
X integration is easy, isn't it just X^2 +C?
Almost: x²/2 + C
Yeah. It's been about 20 years since calculus but ultimately worth going out on a limb for the joke. Thanks.
Take your up vote and get out.
brb pulling up with the riemann integral
This is great news!
🎉🎉🎉
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.
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.
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.
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.
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
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.
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!
When asked for comment, X’s press email replied with its recent standard auto-reply: “Busy now, please check back later.”
What an absolute poop show
To be fair, if I was stuck pooping for over a year like X I would also have that set as my auto-reply 🤷
This is the best summary I could come up with:
Oh 💩
...X, formerly Twitter...
Perhaps one day soon, it will just be
X, formerlyStill waiting for when articles don't feel the need to add that in.
I really wonder why he renamed it to "X, formerly Twitter". /s
Permanently Deleted
“Slack Gives X the Axe”