3 ms·
What "nasty stuff" would Slack being doing that's worth the bandwidth / implementation costs of building a redirect loop in the unlikely case, that 1, the user
by kypro 6y ago
What "nasty stuff" would Slack being doing that's worth the bandwidth / implementation costs of building a redirect loop in the unlikely case, that 1, the user disables JS; and 2, that the user occasionally reenables JS while keeping a non-functional Slack tab open?
- thro1 6y agoSpinning my fan, exhausting battery and memory, segregation by compliance.
- Bjartr 6y agoCan you explain this a bit more? What's the value to Slack to do this?
- thro1 6y agoThose are no values but anti-values. If there is no value to Slack (and others) doing this (even so small as outsourcing costs of processing from their servers to my terminal, measuring differences) could they stop doing this ? There is no need for processing (every time).