Technology

59377 readers

4098 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS

781

Slack gets rid of its X integration (www.theverge.com)

submitted 1 year ago by L4s@lemmy.world to c/technology@lemmy.world

35 comments fedilink hide all child comments

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's thread
view the rest of the comments

[–] Bye@lemmy.world 42 points 1 year ago (4 children)

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.world 23 points 1 year ago (1 children)

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.

[–] 4am@lemm.ee 35 points 1 year ago (1 children)

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.

[–] hperrin@lemmy.world 18 points 1 year ago* (last edited 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.nf 12 points 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.works 6 points 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.world 3 points 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.