Keeping Zulip lean

Stream: Zulip meta

[Sebastian Ullrich]

PSA: hit that "All messages > Mark all messages as read" button at least every few months to avoid Zulip web and mobile downloading thousands of messages on every refresh https://functional.cafe/@kha/110190371390779618

[Kevin Buzzard]

Does this apply to me if I read Zulip several times a day and have no threads/streams muted?

[Eric Wieser]

I assume the danger is proportional to this number: image.png

[Kevin Buzzard]

My understanding was that the issue was if you have something muted then there's a problem which you can't see

[Sebastian Ullrich]

That is correct, but even for the numbers I could see I didn't expect them to be such a network hog

[Sebastian Ullrich]

Eric Wieser said:

I assume the danger is proportional to this number: image.png

No, the "it gets worse part" is that it is proportional to the number of messages since the oldest number included that count (or not included because of muting)

[Gabriel Ebner]

This is a well-known bug: https://github.com/zulip/zulip/issues/21666

[Sebastian Ullrich]

Ah, the good old "report multiple problems in one issue and close it as soon as one of the problems is fixed". But again the title and description are wrong: the number of unreads is irrelevant (though I guess it is a lower bound for the number of fetched messages), only the date of the oldest is important

[Kevin Buzzard]

The fix is clearly not to mute anything

[Johan Commelin]

PSA: You can find a list of your muted topics in your personal settings.

[Alex Vandiver]

Heya from one of the Zulip developers -- and sorry for the bandwidth consumption! This is tracked as #23812, which I'll link from #21666 in case other folks find that issue and are also confused by it being marked as resolved.

If you're interested in the technical planning of what's involved to fix it, see this conversation on chat.zulip.org. We're currently focusing on other work for a 7.0 release in the next month or two, but I think it's possible that we'll be able to start back in on the necessary architecture changes to make progress in that thereafter.

[Sebastian Ullrich]

@Alex Vandiver That's great to hear, thanks! I can understand that this is far from a simple change.