Timeline for Suitable data store for storing comments in a social media site
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 24, 2016 at 7:25 | vote | accept | Pratik Bhattacharya | ||
| Oct 23, 2016 at 22:57 | comment | added | Arseni Mourzenko | @Tymski: well, there was an interesting discussion during one of FogCreek's podcasts about that, when they specifically blamed the tree structure of forums, but I can't find the podcast. In general, when it comes to discussions (and not Q&A, which is inherently different), a tree can in every case be replaced by a list with the ability to quote previous messages in order to keep the track of who you're answering to. For instance, StackExchange's chat follows this pattern (and a chat is a discussion, unlike a Q&A page), making it possible to quote previous comments. | |
| Oct 23, 2016 at 22:24 | comment | added | tmaj | Good point. However, Facebook, The Guardian and many more UX conscious sites allow answers to comments. They enforce limited depth, but it's still a tree. I often find the flat structure of comments on StackExchange, combined with hiding some comments, unhelpful and limiting. | |
| Oct 23, 2016 at 22:14 | comment | added | Arseni Mourzenko | @Tymski: That's not an opinion, but the mainstream opinion in UX community and the opinion of many authors, including the father of interaction design. See for example About Face 3 by Alan Cooper, Tree controls, p. 457 “Unfortunately, hierarchical trees are one of the most inappropriately used controls in the toolbox. They can be highly problematic for users [...]” So no, avoiding using a structure which would be inappropriate anyway in OP's case, I'm not really prematurely optimizing design. | |
| Oct 23, 2016 at 21:49 | comment | added | tmaj | "Flat structure of StackExchange, by opposition to old tree-oriented bulletin boards, is a good illustration of replacing an unusable approach by a very effective one." - that's an opinion only. You're prematurely optimising the design. | |
| Oct 23, 2016 at 20:31 | history | answered | Arseni Mourzenko | CC BY-SA 3.0 |