- cross-posted to:
- technology@lemmy.ml
- technews@radiation.party
- cross-posted to:
- technology@lemmy.ml
- technews@radiation.party
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 must log in or # to comment.
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
I thought this was about Slackware ditching X11 for a moment… which, arguably, would have been a more interesting piece of tech news.
Wayland is the way of the future!
Wake me when it’s the way of the present.
I mean, it’s my presence for about a year and a half
Same here for 2-3 years now, and that’s on a dual graphics Nvidia laptop with the proprietary drivers. I love not having to mess around with xorg.conf!
I’m waiting for them to merge with Yutanee
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.
Removed by mod
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.
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.
🎉🎉🎉
…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
While I know it will not happen, can they revert the UI changes? At least let me declutter the UI 🤢
“Slack Gives X the Axe”
