/0

1698 readers

12 users here now

Meta community. Discuss about this lemmy instance or lemmy in general.

Service Uptime view

founded 2 years ago

MODERATORS

[email protected]

[RESOLVED] Why is ani.social defederated? (ani.social)

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

9 comments fedilink hide all child comments

EDIT: Looks like the defederation has been reversed. @db0 Thank you for looking into this quickly.

A commenter in the linked post is suggesting that dbzer0 automatically follows lemmy.world's block list. That seems like kind of a bad idea? In this instance it seems like the LW admins are just following the decision of lemmy.ml's tankie admins, and tankies gonna tank.

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

[–] [email protected] 7 points 1 year ago* (last edited 1 year ago) (2 children)

Some comment said the defed has been reverted now. For what it's worth, I can access https://lemmy.dbzer0.com/c/[email protected] with no problem.

A commenter in the linked post is suggesting that dbzer0 automatically follows lemmy.world’s block list.

Doesn't make much sense, because e.g. dbzer0 federates with Hexbear, unlike World.

EDIT: I don't understand why people are downvoting OP? It's a normal question.

[–] [email protected] 6 points 1 year ago

Doesn't make much sense, because e.g. dbzer0 federates with Hexbear, unlike World.

IIRC, it's not exactly defederations being looked at, it's actually a specific category of censures logged to Fediseer by lemmy.world admins. The category that lemmy.world admins chose for ani.social is one that is banned on dbzer0.

Whichever bot is handling defederations on dbzer0 simply saw a new site in that category on lemmy.world's Fediseer and auto-defederated it too AFAIK

Hexbear is not in that category so is ignored by the bot

[–] [email protected] 1 points 1 year ago

Hi there! Looks like you linked to a Lemmy community using a URL instead of its name, which doesn't work well for people on different instances. Try fixing it like this: [email protected]