Alien Top
alien.top

I do not want to block all bots. I only want to block bots from specific instance. More specifically, the @alien.top instance is using most, if not all, bot accounts with random usernames. It uses that instance to post in communities of other instances. I thought about blocking other instances. But the main issue lies with random bot accounts from @alien.top. And I cannot block individually by usernames.

What shall I do to block posts posted by random bot accounts of @alien.top instance?

Update

I looked up potentially affiliated sites connected to that instance and found these.

https://level-up.zone/ (@communick, high post rate)
https://gearhead.town/?dataType=Post&page=1&sort=New (same admin, high post rate)
https://viewfinder.pro/?dataType=Post&page=1&sort=New (same admin, medium post rate)
https://netheads.online/?dataType=Post&page=1&sort=New (same admin, low post rate)
https://healthy.community/?dataType=Post&page=1&sort=New (same admin, low post rate)
https://sfw.community/?dataType=Post&listingType=Local&page=1&sort=New (same admin, no post yet)
https://blockchained.world/?dataType=Post&page=1&sort=New (same admin, low post rate)
https://matchpoint.zone/?dataType=Post&page=1&sort=New (same admin, low post rate)
https://poweruser.forum/?dataType=Post&page=1&sort=New (same admin, high post rate)
https://hi-fi.community/?dataType=Post&page=1&sort=New (same admin, medium post rate)
https://expats.zone/?dataType=Post&page=1&sort=New (same admin, medium post rate)
https://nba.space/?dataType=Post&page=1&sort=New (same admin, high post rate)
https://athletic.center/?dataType=Post&listingType=Local&page=1&sort=New (same admin, no post yet)
https://style.land/?dataType=Post&page=1&sort=New (same admin, high post rate)
https://metacritics.zone/?dataType=Post&page=1&sort=New (same admin, high post rate)
https://academy.garden/?dataType=Post&page=1&sort=New (same admin, medium post rate)
https://foodie.rehab/?dataType=Post&page=1&sort=New (same admin, no post yet)
https://indiehackers.space/?dataType=Post&page=1&sort=New (same admin, high post rate)
https://hardware.watch/?dataType=Post&page=1&sort=New (same admin, high post rate)
https://nfl.community/?dataType=Post&page=1&sort=New (same admin, high post rate)

The instances may be hours to two months old and are run by the same admin. Some have high post rate, while others have no post yet. The ones with posts are all using @alien.top’s random bot accounts. I suspect this problem will amplify.

Update2

Blocking by instance is finally working. I blocked @alien.top and @hardware.watch. Consider this issue resolved.

  • rglullisAEnglish
    14·
    11 months ago

    Seems like you want to crowdsource advertising for alien.top.

    Yes and no. Anyone can set up a fediverser instance, and I am certainly not going to let it grow over past 10k “organic users”. My hope is to grow alien.top enough only to validate the idea of fediverser as a migration mechanism and to have more people deploying “fediversed” instances.

      • rglullisAEnglish
        14·
        11 months ago

        I hope people set up fediverse instances instead of fediverser mirror proxies, we need people to communicate with - Not a “shadowbanned” experience for new users where nobody interacts with them.

        You are missing the point. There is no need to have multiple instances doing the content mirroring, and the more people migrate from Reddit, the more I will be able to disable the mirroring.

        The idea is not to get fediverser instances just to mirror more Reddit content. The idea is to get more “fediverser” instances to scale the operation of a coordinated Reddit migration. alien.top itself can not be the home of a million Reddit migrants.

          • rglullisAEnglish
            14·
            11 months ago

            I already stopped the mirrors. What else do you want?

              • rglullisAEnglish
                12·
                11 months ago

                There is no other “place to avoid”. If what bothers you is the alien.top mirrors, then alien.top is your only source of problems. The whole reason that I am creating the content-focused instances (selfhosted, nba, hardware.watch, etc) is to compartmentalize this.