sh.itjust.works Main Community

7709 readers

3 users here now

Home of the sh.itjust.works instance.

founded 1 year ago

MODERATORS

[email protected]

shitjustdontwork. Three days have elapsed without updates to or from our community. (sh.itjust.works)

submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]

45 comments fedilink hide all child comments

I mod a community here, and for the last three days posts made to that community have not been showing up outside of this instance. Specifically, I have an account on Lemmy World, and I can't see any recent posts from the community I mod on that account.

Also, I follow several communities from other instances including lemmy.world and lemmy.ml and none of the content for those communities have updated here in the last three days, though when I check them from accounts I have with other instances, they all show up fine.

I have checked all of this on my mobile browser, my desktop browser, and Jerboa.

Does anyone know what's going on? Does this have anything to do with the steps @[email protected] has been taking to combat bots? This is really problematic, it's like we've been shadow defederated.

Edit: Seriously, why would someone downvote this post?

Edit 2: I'm not sure if this is related or not, but for the first time, I'm not able to respond to a Kbin users comment. That happened in this post.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 9 points 1 year ago (1 children)

They updated to a release candidate for better cpu performance, maybe the performance is a result of not doing everything 😂

[–] [email protected] 6 points 1 year ago (1 children)

I was pretty surprised to see them use a release candidate for a production instance. But, what do I know

[–] [email protected] 10 points 1 year ago* (last edited 1 year ago)

We were actually one of the last servers to upgrade to 0.18.1 RC. And now we are on the release version. I'm not sure about the federation issues but I thought it was due to lemmy.world and lemmy.ml being overloaded, and not a problem coming from the sh.itjust.works side.