this post was submitted on 18 Nov 2025
13 points (88.2% liked)

Sopuli's Default Community

1350 readers
44 users here now

Community for all jibber-jabber. As this is a hard-coded community for every instance, we may get this doing something useful.

Simple test posts to !test_community@sopuli.xyz

Meta-discussion regarding the instance and support in problem situations !meta@sopuli.xyz


Yhteisö kaikenlaiselle pälätykselle. Koska tämä on kovakoodattu yhteisö jokaiselle instanssille, voimme tehdä tällä ehkä jotain hyödyllistä.

Yksinkertaiset testiviestit mielellään !test_community@sopuli.xyz

Instanssia koskeva metakeskustelu ja tuki ongelmatilanteissa !meta@sopuli.xyz

founded 4 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] IcedRaktajino@startrek.website 12 points 22 hours ago* (last edited 22 hours ago)

Not that this makes any of the other answers wrong, but the actual answer is that it was probably a 30-day temporary instance ban.

When a remote account is instance banned, it's automatically banned from any communities on the instance it has interacted with and uses the same expiration date and reason as the instance ban. Lemmy does that automatically in the backend.

If you're viewing the modlog from another instance, however, you don't see the instance ban (only the community bans federate) so it makes it appear the mod is having a hissy fit.

Again, and given the instance involved, this does not mean any of the other answers are wrong, lol, just incomplete.