[don-code]

Slack additionally decides to hard-reload itself, seemingly without reason.

I work on the road (from a train / parking lot / etc) for five or six hours per week. My T-Mobile plan is grandfathered in, so I can't "upgrade" to a plan that allows full-speed tethering without considerably impacting my monthly bill.

Realistically, I hit around 1.5Mbps down. When Slack reloads itself, I have to stop _everything else_ that I'm doing, immediately, and give Slack full usage of my available bandwidth. Often times, it means taking my phone out of my pocket, and holding it up near the ceiling of the train, which (I've confirmed in Wireshark) reduces my packet loss. Even then, it takes two or three tries just to get Slack to load.

[djtango]

I feel your pain - one minute you're reading some messages or a note and the next you're locked out of slack with faded screens and infinite spinnies.

Apparently we must be very niche amongst their user base because these kinds of fixes hasn't made it onto their roadmap in years

[fragmede]

I wonder if you could stick your own root CA into your OS'S certificate store and then MitM the connections slack makes, and then respond no don't update with burpsuite and cache with squid to alleviate the problem.