this post was submitted on 25 Oct 2023
774 points (98.5% liked)
Technology
59594 readers
3118 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
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.