Not yet. I’m still waiting for my registration on fedia to go through. If not I’ll go with the other instance then subscribe to it there. Or I might just do both. ¯⁠\⁠_⁠(⁠ツ⁠)⁠_⁠/⁠¯

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 !fitmoe@lemmy.world thru that instance, I saw the notice.

Edit: I don’t think it’s the community that’s broken. It seems quite active. It’s probably like what e0qdk said in another reply.

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!

SurprisedPikachu.png