Email or username:

Password:

Forgot your password?
Top-level
Chris Trottier

To give an idea about why ai.wiki should be put on #Fediblock, take a look at their about page where they trumpet “benefits to businesses”.

ai.wiki/about

The so-called “business” they attract are spammers.

Take a look at their local feed, and you’ll quickly surmise that this server exists for spam.

ai.wiki/public/local

Bots and spammers are here. Thankfully, we have tools to combat them.

5 comments
Comrade Weez

@atomicpoet thanks for the heads-up. Definite #fediblock candidate. I blocked the domain as a temp measure.

DELETED

@atomicpoet Thank you. I've gone ahead and blocked the entire domain so it will never show up in my feed. Here's hoping #Fediverse server admins all over do the same.

Elias Mårtenson

@atomicpoet I'll probably block this myself if I see it in my feed. That said, the content on its own doesn't necessarily violate many policies to the point where it belongs on a global list.

Of course, if the accounts on the instance actually starts spamming then I'll immediately change my mind.

That said, I think you're eventually going to be right, since there is zero profit in posting on just the timeline of an instance that contains nothing but marketing. You need reach, which will drive these people to spam. However, that spam is what should get them on the lists, not the mere fact that they have a feed full of marketing.

@atomicpoet I'll probably block this myself if I see it in my feed. That said, the content on its own doesn't necessarily violate many policies to the point where it belongs on a global list.

Of course, if the accounts on the instance actually starts spamming then I'll immediately change my mind.

That said, I think you're eventually going to be right, since there is zero profit in posting on just the timeline of an instance that contains nothing but marketing. You need reach, which will drive these...

Go Up