{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
2/8/2013 7:32:30 PM
10
Unless the Bungie employee "flashes their badge" and that will change the entire topic to have a golden septagon. At least as I understand it, employees have that option. I don't know if the option exists in replies as well as OP's they make.
But since your question is clearly stated in the OP, and you properly tagged your OP. If 3 months from now someone is that intent on performing a search rather than asking the same question again, that thread could be found and read for the solution/answer.
Or is your point that because the thread isn't flat, it "hides" content that otherwise would be found by a visual scan of the flat thread?
English
-
[quote]Or is your point that because the thread isn't flat, it "hides" content that otherwise would be found by a visual scan of the flat thread?[/quote]I'm not going so far as to provide a solution to the problem (like reverting to a flat structure), but that is basically my point. This case happened to involve a Bungie employee, which is why I felt it was a good example, but that doesn't need to be a case. The point is... There is often valuable discussion that takes place within the depths of reply chains that is likely relevant and if interest to everyone who views or posts in the thread.
-
[quote] Or is your point that because the thread isn't flat, it "hides" content that otherwise would be found by a visual scan of the flat thread?[/quote]Ding ding ding. Also why I hate the new reply layout. I agree with the first post as well.
-
But flat threads have their own inherent flaws as well. They don't handle disruptions well (for one). I've seen a 1,000+ reply thread here in this model that was terribly spammed inside of one comment-tree. The rest of the thread kept going as if there was nothing wrong at all. The compartmentalization of comments and their reply-trees were like water-tight compartments on an ocean liner. One compartment was breached and flooded, the others kept dry and the thread didn't sink (or get closed). A flat thread would have had to been put down for its own good.
-
I think it would feel a lot less separated if comment trees weren't automatically collapsed. Indent and perhaps even color code each tree, but don't collapse them. That way, if I don't care about a comment tree, I can just scroll past it, or collapse it if I don't want to follow it, but I don't have to go back and forth trying to reopen comment trees that I keep track of, or have yet to post in.
-
I enjoy this version. Let me collapse things as I see fit, but for starters let me see everything.
-
Sadly, Achronos I thiiiiink just mentioned that comment trees that are collapsed haven't been loaded yet, saving space or something. I'm too tired to sound smart right now.
-
I agree and think this would go a long way to adressing people's frustrations.
-
I think the ability to toggle back and forth, or the ability for individual users to choose their preference, would be the best option.
-
I'm not saying this system does not have benefits. And I'm not saying the old one lacks flaws. But even despite the ill-intent of people to ruin threads before, I found that in the vast majority of threads I could indeed actually follow the conversation. I could reply to multiple users at once. I could read and know what came when. The current system isn't horrible, and I see the logic behind it. But I just cannot deny that it is messy and I feel like the community is stagnated (that word fits here, right?). Separated from each other. I just don't like it. Eh.
-
Fair enough. I too am seeing the good the bad and the ugly of our historic system and the new one. Our ability to compare notes is (IMO) very helpful in better understanding some of those issues. It keeps us all from romanticizing the old OR loving the new just because it's new.
