Slack gets rid of its X integration
![](https://lemmy.world/pictrs/image/7c668ec0-a3ad-455f-b736-1f5f13808b09.png)
![](https://fry.gs/pictrs/image/c6832070-8625-4688-b9e5-5d519541e092.png)
![Slack gets rid of its X integration](https://lemmy.world/pictrs/image/eab5fa31-8779-4333-ab1f-e93ae73b1645.jpeg?format=jpg&thumbnail=256)
theverge.com
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.
You are viewing a single comment
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.
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.