sunaurus

I temporarily transferred the community to myself and was able to undelete it. I've transferred it back to you now, should be all good.

They are using an allowlist rather than a blocklist, unlike most big instances. We are linked, but we're not on their allowlist, so the result is still that they block all federation from lemm.ee.

Can you try logging in first at https://next.lemm.ee/login - or are you seeing this while already logged in?

Aha, I think this restore feature is missing from the standard Lemmy UI.

Maybe this will help: I quickly implemented a very basic restore button on lemmy-ui-next. Can you check if you see a "Restore" button in the sidebar at https://next.lemm.ee/c/eurographicnovels? Note that you must be logged in as a moderator to see this button.

I need to step away from my computer for a while, but if this doesn't work, then I will be able to look into it further during the weekend.

Purging is something that can't really be used to hide mod actions, as any federated instances will still retain their copy of any purged content. Purging is a feature which is only really useful for completely removing illegal content from our servers, it's used quite rarely and in fact leaves a trace in the mod log as well.

Just to clarify a few things:

1. Our mod log will show all federated mod actions, not just actions by lemm.ee mods and admins. So if any other instance is generating a ton of actions, it will also be visible from our mod log. In fact I don't think there has been any increase recently in lemm.ee mod actions at all.

2. The mod log does not actually get cleared, there is simply a UI issue in Lemmy which makes it a bit hard to view the mod log chronologically. The UI makes it appear as if the mod log is one single list of actions, while in fact it's different lists combined together (one list per each action type). You will notice some really old actions even on the first page of the mod log, this makes it seem as if there is a "missing period" in the actions, while in fact you are actually just seeing the first page for each different action type. If you navigate to subsequent pages, you will find all the "missing" actions there.

In practical terms, it's not really possible to clear the mod log at all, thanks to federation. Even if one instance will delete their local mod log records, those records would still be visible in other instances which they previously federated out to.

I agree that using the mod log to attack other users with inaccurate mod action reasons is not really justifiable.

We now have some additional guidance about this here under the moderator responsibilities section:

Ensure that they only provide accurate and clear reasons for mod actions

I will make a separate announcement post about this as well shortly.

Unfortunately, due to the nature of mod log federation on Lemmy, it's not really possible to retroactively change mod action reasons currently. I am sorry about that. If this does end up causing problems for you in the future, you could point people to this thread for context.

Hey, indeed it appears that the community was somehow removed by you:

Notice it says "Deleted by creator" .

Can you check in the top right corner, in the area visible in my screenshot, is there not a small "Restore" link? This should in theory let you un-delete the community.

We had a temporary delay with outgoing federation. Everything should be recovered and back to normal now!

We had a temporary delay with outgoing federation. Everything should be recovered and back to normal now!

Yes, they indeed blocked us a while ago, AFAIK it was planned as a temporary thing, but no idea where they stand on it now.

Hey! Do I understand correctly that your app is trying to fetch any /post/<id> directly from its source instance API? If so, I have a few ideas:

1. If you detect anything that looks like a Lemmy post URL (<host>/post/<id>), you could first try to make a request to <host>/version, and only treat the post as a Lemmy post if you get a JSON response from that endpoint where .software.name === 'lemmy'. Otherwise, open that URL in the browser.

2. The above will already "fix" the issue, but custom frontends on subdomains is actually quite common, so if you want to handle those links without resorting to a browser, then: in cases where <host>/version is not a Lemmy response, but <host> includes a subdomain, you could repeat the same logic from step 1 for the parent domain as well. If you detect a Lemmy API at the parent domain, then just use that to fetch the post.