You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm signed into two instances. When one of the instances timed out earlier today — that's at least what I think caused this — going to the "everything" feed just showed a little spinning loading ring. When this happened, I went to look at an instance feed of an instance I knew wasn't timed out, but alas, the spinning ring was still there, and I think was eventually replaced with something along the lines of "unknown error". When I went into my list of subscribed communities, the spinning ring was there as well — and was eventually replaced by some sort of 504 error message involving the Lemmy API. Upon starting and restarting Liftoff, the feed from the working instance loaded just fine — it was only after attempting to open the everything feed that the working instance's feed also broke.
What I would at least like to happen is that if one instance is to time out, that attempting to open the everything feed or subscribed communities list would give a little message saying something like "[instance name] is unresponsive; disabling temporarily", essentially ignoring that instance until it becomes responsive again.
The text was updated successfully, but these errors were encountered:
Windows 10, ASUS TUF Gaming F15, Liftoff 0.10.10
I'm signed into two instances. When one of the instances timed out earlier today — that's at least what I think caused this — going to the "everything" feed just showed a little spinning loading ring. When this happened, I went to look at an instance feed of an instance I knew wasn't timed out, but alas, the spinning ring was still there, and I think was eventually replaced with something along the lines of "unknown error". When I went into my list of subscribed communities, the spinning ring was there as well — and was eventually replaced by some sort of 504 error message involving the Lemmy API. Upon starting and restarting Liftoff, the feed from the working instance loaded just fine — it was only after attempting to open the everything feed that the working instance's feed also broke.
What I would at least like to happen is that if one instance is to time out, that attempting to open the everything feed or subscribed communities list would give a little message saying something like "[instance name] is unresponsive; disabling temporarily", essentially ignoring that instance until it becomes responsive again.
The text was updated successfully, but these errors were encountered: