"Other timelines" has a bug with IDs anyhow, they must be unique which is not currently enforced. So use a prefix in their ID that always sorts last? Group chats always sort before person chats but within the same type it goes by ID or Name. If this is all too hacky, we should think of allowing protocols to specify their own sort algo, the current generic one sits in ChatTreeView.SortTreeStore()...