Button to mark read gets pushed off when the username is too long.
At least there’s still a mark all as read at the top. Tangent, I wanted to post using the app but I can’t navigate to the magazine using interstellar. Keep getting 500 internal server error on the fav side bar or unknown error when trying to explore.
I’ve decided to sign up with fedia.io, but somehow still waiting for my application to be approved.
So I checked with the next biggest mbin instance, kbin.earth. When I checked out [email protected] thru that instance, I saw the notice.
the second message means that no one is subscribed to the community locally, so your instance isn’t getting updated by the remote source any more.
I see. I saw this mentioned before when I was researching on the threadiverse again recently (is that term still in use lol). It’s no biggie, if that means I can help bring it up to date on that instance, I’m happy to do it.
Thanks!
mbin instance looking at lemmy community showing "magazine [community] is not receiving updates"
tl;dr: what does it mean to see these two warning/notice saying “This magazine [community] is from a federated server and may be incomplete.” and “This magazine [community] is not receiving updates.” Hello. I’ve tried to get into lemmy back when reddit did the API restriction and killed access to my favorite Sync for Reddit, and it kind of really didn’t stick. Now I’m trying to get back into the threadiverse and figured I’d try with mbin now since I’m more keen to have an account that’s seemed to have good mix of “properly” showing and have access to threads and microblog posts. But some instances of mbin seem to have the one or two warning/notice on top of the community page. I’ve looked at the community both thru two top mbin instance and through the community’s local instance and yeah the warning is right. One of the mbin instance aren’t synced / updated. What does it actually mean, and how will it impact my browsing? Thanks.
