I found an active thread in a sub on another instance I’d like to participate in. When I sub to the thread from sh.itjust.works there are no comments; I assume that’s because sh.itjust.works only starts syncing communities after the first subscription. So now I can either read the thread on an instance I don’t have a login for, or participate in an empty version of the thread on sh.itjust.works.
Is there any way to participate in the active thread at this point? Thanks.
edit: Just checked my subscription to the new community is [pending]. Maybe that’s it?
edit2: Thanks to @Barbarian I can at least sub to one of the pending communities, and the others are on lemmy.ml, so I’ll just wait those out.
If the pending subscription does sort itself out in a minute or two, and the Lemmy server hosting the community isn’t broken right now (test by visiting it’s homepage in a browser), then you can click the pending button to unsub and try to sub again. Retrying like this is how I sorted all my pendings, though obviously be chill and don’t do it a million times and generate million subscribe messages if something is legit busted.
I have about a half dozen pending subscriptions, and have tried a few times to unsub then resub over the past 24 hours to them to no avail. I’ll keep trying. But they’re not all on the same server.
Fair enough. It’s really hard as a user to determine the difference between a bug on your instance and weirdness due to all instances being sluggish and heavily loaded. I don’t have more advice beyond give it time and retries, but I empathize with your frustration. It’s all a bit strings and bailing wire right now, but if you watch the githubs contributions from very sharp experts are flying in at record pace. Hopefully it gets better (though I don’t have a GitHub issue to point to for this problem).
Oh it’s not that big a deal. I guess it sounds like I’m frustrated, but text can be like that. I’m just trying to figure some things out. And it turns out that all but one of the pending subs are on lemmy.ml, so it really is likely a server-side issue.