Tlaster

> So Twitter identifies and assembles all the messages from threads (messages responding to the previous one of the same user, in a specific time span for all messages or...

Not sure how to resolve this issue since we don't have a chromebook yet. Again, is this a Twidere X issue or the old Twidere issue?

Twidere comes a long way since the first commit in 2014 (8b0b3f47b968adada2b6d927901ccec1ba4991a4). 6 years later, things changed, Twitter announces its brand new V2 API, Android app development continues to evolve...

It's here https://github.com/Tlaster/moko-spotless-conflict I think it might have a conflict with spotless, I can not apply moko resource with spotless at the same time.

Just note that @HuixingWong is an external contributor and we appreciate his hard work for Twidere X. Custom theme support is under consideration, but we prefer using a pure compose...

Thanks! Could you please try the beta version from google play? Does beta version have the same issue?

It's almost a month later and during the time I can not reproduce the issue, maybe it is just the Twitter API that returns incorrect data. Can you provide the...

Never mind, this is just in case you're using a custom API key to log in. And could you please check if this issue happens on original Twidere?

Thread is a little bit complicated, the Twitter API does not return the same order as the web page, and it's hard to choose the right order since the API...

> I've test Nitter today (nitter.net). I don't see any thread enhancement. Am I using the appropriate url for nitter ? Nitter support can do some help on the thread,...