Gregory's Server@cdevroe So seems like a connection is at least being made! If you click on it, do you get information about messages sent through the connection?
|
5 comments
 @cdevroe If that's the case, I wouldn't know what to do about it. If the websocket connection fails, there's a retry mechanism, plus a polling fallback. If the browser kills the page so none of that happens that's outside my expertise 😦 @cdevroe But yeah in the JSON stream you'll likely see events like "subscribe" and "unsubscribe". If there's no "subscribe" event or an unexpected "unsubscribe" event then it could be another reason why you might not receive any new toots.  @Gargron Following up on this thread, this morning I got this message even though my computer was plugged in: @Gargron I wouldn't expect you to be able to fix that, that's for sure! It appears that Webkit - and other browsers - have a feature called background tab throttling. One Chrome et. al you can shut it off. But Safari doesn't have a preference for that unless you use a preference rewrite via Terminal. If I come across anything that will help keep Mastodon alive even if Safari tries to kill the connection I'll update this thread. |
@Gargron Looks like it has a few tabs. Preview shows the JSON stream, Headers, Cookies, Sizes, Timing and Security. That all seems to be working at the moment. My bet is that if I leave this pinned tab for some amount of time, Safari will eventually "shut it off"