@apps I'd really really want it to be in chronological order...otherwise I'd probably not use it...and I LOVE the color of each post would reflect which account it was from.
Conversation
Notices
-
Embed this notice
Chris Ferguson (chrisferguson@mastodon.social)'s status on Saturday, 04-Feb-2023 06:50:35 JST Chris Ferguson -
Embed this notice
Fedilab Apps (apps@toot.fedilab.app)'s status on Saturday, 04-Feb-2023 06:50:34 JST Fedilab Apps @ChrisFerguson
Why you won't use it without a chronological order? It's like having the same pagination for all accounts but the date at the top won't make sense.
If we use chronological order, how to deal with active and less active timelines? One account could have three paginations before we display first messages of another account.
With all the difficult logic to discard them before the date matches to embed them in the timeline. -
Embed this notice
Chris Ferguson (chrisferguson@mastodon.social)'s status on Saturday, 04-Feb-2023 07:01:16 JST Chris Ferguson @apps
I'm not sure if I'm understanding what you're suggesting with pagination.The way I'd picture an ideal merging of time lines would be each post loaded in chronological order, and the background color of each post being representative of the account that post was from.
The reason I like chronological order is because I'm worried I'd miss something, or read something in the wrong order. I hope that helps!
-
Embed this notice
Fedilab Apps (apps@toot.fedilab.app)'s status on Saturday, 04-Feb-2023 07:01:16 JST Fedilab Apps @ChrisFerguson
That needs more logic behind. Let say you have an account that follows active users so with an active home timeline and another one without such interactions.
That means the app will fetch first page for each account.
But for second account it should stop fetching because no messages can be injected (delayed dates).
The only solution to build that properly would need that mastodon allows to paginate with date and not Id.
-
Embed this notice