Twidere-Android
Twidere-Android copied to clipboard
TwidereProject
Thread are not working again (v4.1.4)
Looks like threads has stopped working again in the latest version. Replies to the thread are shown first then thread tweets It was working fine a few days ago, so could be that Twitter changed something?
I think the threading should be close to the official websites with multiple branches of replies and replies to these replies. In addition to that i think we should collapse messages that are threaded replies to each others and just tell a coherent story. Especially when we have thread indicators inside like /1 or (1) or whatever certain other clients use to mark them. Even more when there are no replies to certain "submessages" of the thread. A local version of ThreadReaderApp so to speak.
On some tweets, no thread follow ups are shown at all, on others only the first follow up is shown and you need to tap it to see another followup, etc.. This can be best seen on threads that don't have any (other) replies.
Looks like the only way to read a thread now is "Open in browser", with all the shenanigans of Twitter web... 😒
@ge0rg I don't know if it is a temporary thing, but "Open in browser" now often gets me a "Cannot Complete Request" error page...
@ccoenen I may have found out. In Firefox' "Enhanced Tracking Protection" (tap shield left of the URL bar, then "Protection Settings" I had set it to Strict. When I put it to Standard, twitter works. (The non-mobile version also works, but the letters are too small). It snows "google-analytics" as tracking content. I think uBlock Origin blocks that already without breaking the page.
As we're working with the new Twitter API V2, we're trying to fix the thread issue, but there's still no specific API for it
Isn't that covered by https://developer.twitter.com/en/docs/twitter-api/conversation-id ?
Isn't that covered by https://developer.twitter.com/en/docs/twitter-api/conversation-id?
Yes and no. we do use this API to resolve thread in TwidereX. It does return the thread information we need, but with some limitations. If you take a look at the Recent search API document,
The recent search endpoint returns Tweets from the last 7 days that match a search query.
It means that if the tweet is 7 days earlier, this API will not return any result. Also, we've found that this API still having some issues, like some tweets that in the thread won't return from the API, or return with some tweets not found errors while the tweets are there(not been deleted). And If you notice, nowadays's Twitter's thread is a tree, and this API returns a list with pagination, while building a tree upon this list is easy, making the thread looks reasonable is hard since this API will return in reverse-chronological order. If a tweet gets lots of replies, 1000 for example, the thread will look quite weird.
Well if a tweet has lots of replies it will need constraints regarding number and time to not be a total mess. Threaded view or not. ApiV2 is in flux and https://twittercommunity.com/c/twitter-api/twitter-api-v2/65/l/latest still collects feedback , questions and bugs. That part should be solvable.
Opened Aug 22 2020. A whole year has passed. Still no solution. Sad. Where in the hell is the problem? I'm on 4.1.8.
Here an example: https://mobile.twitter.com/Medicilio/status/1419580377425928193
¿Os anyone working on it?
