It’s a known bug in Sync with Lemmy 0.19.5:
https://github.com/laurencedawson/sync-for-lemmy/issues/539

lemmy.world is still on Lemmy 0.19.3.

At one time they had open registrations, so spammers were taking advantage and setting up shop there. It looks like the instance now has a sign-up application. I have unblocked them. Thanks for noticing!

This is a good opportunity to remind users about our Fediseer profile: https://gui.fediseer.com/instances/detail/sh.itjust.works
We try to keep our Censures list on Fediseer up to date with the sh.itjust.works instance blocklist. That way we can leave notes in Fediseer explaining why each instance is blocked.

I’m expecting ponies. So many ponies.

Thanks for the heads-up. They’re gone now.

I’m definitely interested in hear other people’s opinions. Posting something in the Agora seems like a good idea. If nobody in this thread does it then maybe I’ll put something up myself in a few days.

For now, @imaqtpie@sh.itjust.works’s suggestion is the way to go: PM one of us admins on a case-by-case basis and we’ll help out.

In the long term, maybe we should set some criteria for identifying dead or unmodertaed communities and locking them? Our instance has hundreds communities, many of which are hardly used and likely abandoned by their creators. I made an effort some months ago to find active mods for the busiest communities, and remove communities with no assigned moderator. I’m not sure what to do with the rest of them, if anything. They aren’t causing immediate problems. And confirming the activity status of every mod is one of those dull chores that has lingered at the bottom of my to-do list.

Some of the instance admins have been poking at this lagging federation issue for a few weeks now, trying to figure it out.

The Reddthat admin noticed that Lemmy’s federation process can’t seem to meet demand in some cases. Reddthat has had trouble staying current with lemmy.world due to the network latency between Europe and Australia: https://sh.itjust.works/comment/9807807. I understand that lemmy.nz has seen this, too.

Another thing that has been noticed is spamming of actions from kbin instances. It looks like some process gets stuck in a loop on the kbin side. https://lemmy.world/comment/8961882

I’m sure there are other contributing problems that still aren’t well understood. This software is a work in progress, after all.

c/shadowrun was deleted by its creator. It was pretty quiet: 33 posts total, and only 1 post in the last 5 months.

If you want to cultivate a Shadowrun community, I could purge the old one and you could recreate it from scratch.

Though admins can see the deleted community, lemmy-ui does not give the option to un-delete it, unfortunately. It would take some work to see if that’s even possible through the API.

Are you still having problems logging in? Our server was having issues around the time you posted this.

That FediDB stats page is confusing. It isn’t clear whether they only count instances that have joined Fedipact, or also include instances that have blocked Threads without joining Fedipact. A quick glance at the list suggests the latter. But in that case, there are a bunch of instances missing from the list.

The list on the Fedipact site is a better source:
https://fedipact.veganism.social/

As for admins versus users, here on sh.itjust.works we held a vote among our users. The result was overwhelming: 78% of users voted to preemptively block Threads.
https://sh.itjust.works/post/11308397

(Edit to fix some awkward phrasing.)

Welcome!

Lemmy instances are in the middle of transitioning to a new version (0.19.x). It’s been a bit bumpy. You might notice some changes once this instance upgrades. We’ve been holding back until we’re confident that the new version is stable.

If you need to contact the admins you can message us directly. Or, for a faster response, get into our instance’s Matrix chat: https://matrix.to/#/#sh.itjust.works:matrix.org

Here’s a screenshot of my view of the post to illustrate what I was trying to describe. The user you were replying to deleted their comment, which results in the whole comment tree becoming hidden.

I agree there’s some other weird stuff going on, too. This morning I received a user report that was days old. I’ll let TheDude know.

Left a response in the linked thread, but am copying it here, too:

From my view the original comment has been replaced with “deleted by creator”. If a user deletes a comment in Lemmy 0.18.5 then it and all its child comments are removed from public view. Though @AMillionNames@sh.itjust.works will still see their own comment in the comment history section of their user profile. I think that this behavior will change when we upgrade to 0.19x, and non-admin users will see “deleted by creator” as well.

There appears to be something else going on, too. If you view the post from lemmy.ca or literature.cafe (both of which are on Lemmy 0.19.1) the original comment is still there. It’s like those instances never got the memo that the comment was deleted. I can only assume this is related to the ongoing federation issues in Lemmy 0.19.x?

From my view the original comment has been replaced with “deleted by creator”. If a user deletes a comment in Lemmy 0.18.5 then it and all its child comments are removed from public view. Though @AMillionNames@sh.itjust.works will still see their own comment in the comment history section of their user profile. I think that this behavior will change when we upgrade to 0.19x, and non-admin users will see “deleted by creator” as well.

There appears to be something else going on, too. If you view the post from lemmy.ca or literature.cafe (both of which are on Lemmy 0.19.1) the original comment is still there. It’s like those instances never got the memo that the comment was deleted. I can only assume this is related to the ongoing federation issues in Lemmy 0.19.x?

Yes! Thanks to everyone for making this place great. Here’s to a great year ahead!

It appears this behavior is fixed in Lemmy 0.19.1. Look at the same post via an instance that has upgraded: https://lemmy.ca/post/12129776

Our instance hasn’t upgraded to 0.19.x yet. We’re waiting for outgoing federation to be fixed: https://sh.itjust.works/post/11532242

It looks like a user deleted their comment, causing the subsequent responses to not be shown. When I view the post from my admin account it’s all still visible to me (see the screenshot below). Though if I view the post from a non-admin account then the deleted comment and all its children are not shown.

I agree that this is weird behavior, but I think it’s by design. In this case I would prefer that Lemmy show everyone the “deleted by creator” note and keep the rest of the comment chain visible. I am not aware of any server or community settings to change this behavior.

It’s interesting that Mastodon instances are trending in the opposite direction of Lemmy instances. Most are staying federated with Threads. I wonder if that’s simply indicative of the strong anti-corporate culture on Lemmy, or if there’s more to it.

Meta doesn’t need to bother with back-channel influence peddling of existing instances. If Meta simply opened its own Lemmy instance it would immediately be the largest Lemmy instance by orders of magnitude.

Making a post here will work. Though for the fastest response you should get into our instance’s Matrix chat: https://matrix.to/#/#sh.itjust.works:matrix.org

I don’t expect Beehaw to refederate anytime soon. As of last month they were still considering moving to another platform: https://beehaw.org/post/9558079

As for infosec.pub, I’ll chat with the other admins about inviting them to refederate. My understanding is that they were getting a lot of reports related to our instance and decided to pull the plug on us.