Not only does it completely overload the browser during longer conversations, but I honestly don’t understand how a multi-billion dollar project can have such a poorly designed system. What’s the point of message branching if there’s absolutely no basic way to navigate it afterward? You have no chance of figuring out which message has more children. The idea of a branch map? I won’t even go there—that would be asking too much, apparently. But come on, why not at least mark messages with multiple children using an icon or a color? This is amateur hour at its finest.
So if I get lost and need to find a message that’s in a hidden branch, I literally have to download the JSON, search it locally on my computer, and then track down the corresponding parent message manually… A 14-year-old could’ve built a better interface.
Oh, and it’s just brilliant that there’s a search function on the website, but what good is it if it finds the correct message and then doesn’t even show it in the chat window because it’s in a collapsed branch?
It’s painfully obvious why it’s made this badly—because doing it right would require programmers who can actually think logically, and apparently, those in this part of the world all want a million a month.
Sorry, but come on—recursively expanding a chat thread, or at the very least highlighting where the conversation branches off… what the hell? Are we living in the '90s? Back then we would’ve had a better product.