- Twitter having a broken service worker (saw this a lot on Twitter discussions in last weeks)
- Safari perhaps lowering the JS execution priority in background tabs
- Twitter trying to be nice and only exec JS while their page is in foreground, and hitting a bug in Safari regarding visibilitychange callback not firing (which is fixed in Safari 14 by the way)