Ancestors

Written by Alex on 2025-01-01 at 19:46

@ivory Why is it, that when I send a toot, refreshing the main feed will sometimes not show it for a long time (like half a minute even with constant manual refreshing)? In the web UI of Mastodon it’s pretty much immediately there once it’s sent.

=> More informations about this toot | More toots from lx@swiss.social

Toot

Written by Alex on 2025-01-19 at 12:18

@ivory This is still happening with the latest version. Before #Ivory would show the toot I just composed, I was able to open a new tab in my browser, navigate to my instance and read the too there. All while Ivory was still acting like there are no fresh toots to show. After another minute it magically appeared when I tried refreshing for the 10th time 😂

[#]Mastodon

=> More informations about this toot | More toots from lx@swiss.social

Descendants

Written by Ivory by Tapbots :emoji_wink: on 2025-01-20 at 15:03

@lx Mastodon has API limits so we don't actually refresh every time you pull-to-refresh because then you'd end up getting rate limited. We allow a server request a certain amount of times a minute. The website uses a streaming API so it's very different.

=> More informations about this toot | More toots from ivory@tapbots.social

Written by Alex on 2025-01-20 at 16:58

@ivory I remember getting rate-limited on the website in the past and it wasn’t a big deal but I can understand the reasoning.

Maybe some special setting somewhere so the user could choose to propagate all calls immediately?

Or could the streaming API of the website be implemented in #Ivory as well?

=> More informations about this toot | More toots from lx@swiss.social

Written by Ivory by Tapbots :emoji_wink: on 2025-01-20 at 17:11

@lx We will look at streaming eventually, but it's all very complicated especially when remembering your last read location is important.

=> More informations about this toot | More toots from ivory@tapbots.social