This repository was archived by the owner on Jan 23, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Jan 23, 2023. It is now read-only.
Display replies below tweet #16
Description
Baedert chose to put replies above the tweet in tweet view, so you have to scroll up to see them. This seems odd and is the opposite of what Twitter (and almost every other threaded UI) does.
I should finally get round to making the change to flip it so that it reads the "right" way (scroll up to see previous posts in thread, replies are automatically visible).
(Reported by @jacobmischka as baedert/corebird#369 and backed by me but rejected in Corebird)
Reacted by Lenny., Yousuf 'Jay' Philips and Ezwen
Activity
[-]Reverse tweet order for replies[/-][+]Display replies below tweet[/+]LennyPenny commentedon Nov 4, 2019
Any progress on this?
IBBoard commentedon Nov 4, 2019
No, not yet. You'll see commits appear in this ticket or a branch called "bug-16-blah-blah-blah" when I start working on it.
I've looked at it before in the Corebird days but never took it too far because Baedert didn't want it. In some ways it should be quite easy, but in others then I think it needed some reasonable thought to be done properly.
Re #16: Add a helper method to tweets
Re #16: Add asc/desc sort order to TweetModel
Re #16: Restructure TweetInfo page
Re #16: Make hidden content scroll in bottom-first
Re #16: Remove unused ReplyIndicator
IBBoard commentedon Apr 12, 2020
Okay, I think that branch fixes it. I'm just running it locally for a while to make sure.
Any feedback on it is welcomed (e.g. whether we need more of an indicator that there's "replied to" tweets above, even though the tweet says "in reply to X")
Re #16: Fixed tweet rearranging on thread clicks
j1warren commentedon May 6, 2020
Oh, just remembered what I wanted to ask for a while.
cawbird doesn't load all the replies for a tweet when you open one.
For example, link
On the twitter.com page it shows 6 replies, however cawbird for me displays only 2.
Is that how it supposed to work?
IBBoard commentedon May 6, 2020
That's more relevant to #17.
The short answer is that a) there's no official way to get the replies to a tweet (limitations) and b) the best approximation we have uses the search and is limited to 7 days of history and a few other constraints (again, limitations!). The time limit isn't relevant here, but I imagine some of the other constraints area.
Hashtag-Blame-Twitter-API-Again
Re #16: Add more tests to tweet model
Re #16: Rename and test "remove oldest" function
IBBoard commentedon May 30, 2020
Fixed and merged when we merged #17
Re #16: Add a helper method to tweets
Re #16: Add asc/desc sort order to TweetModel
Re #16: Restructure TweetInfo page
Re #16: Make hidden content scroll in bottom-first
Re #16: Remove unused ReplyIndicator
Re #16: Fixed tweet rearranging on thread clicks
Re #16: Add more tests to tweet model
Re #16: Rename and test "remove oldest" function