During the last two days it seems we have been “bombarded” with advertisement bots.

I found it curious, the advertisements are correctly targeted to sysadmins and security professionals. Meanwhile they have somewhat believable biographies (even if they are a little on the nose), suggesting hand crafted accounts.

Something they all have in common is their instance (discuss.tchncs.de) and that they have a “bachelors degree in computer science”.

This is not the first time I’ve seen adbots on Lemmy, but it’s the first time I’ve seen them on infosec.

Does anyone have any insight into the world of adbots they could share? I find myself increasingly curious in what goes on behind the curtains.

  • Deebster@lemmyrs.orgEnglish
    0·
    1 year ago

    Seems like Lemmy should add a rel=canonical link when browsing federated communities - this would “solve“ this issue (and would be the correct thing to do anyway).

      • Deebster@lemmyrs.orgEnglish
        2·
        1 year ago

        No, I was referring to the bit about having lots of copies of the same content on each different instance. If example.com/c/comm@* had a meta tag giving the origin community as the rel=canonical link target then only the origin would be in a search engine as the only linker.

        rel=nofollow is a good idea too, but less interesting to this semantic html nerd.

    • jonne@infosec.pubEnglish
      01·
      1 year ago

      I believe Lemmy instances disallow crawling by default, so SEO is probably not why. Would be nice to find Lemmy results in Google if they can sort out the canonical URL problem. Reddit was a great resource for random questions, and if people move here it should still be easy to find.

      • Deebster@lemmyrs.orgEnglish
        1·
        1 year ago

        What makes you say that? robot.txt just disallows things like /create_community and there’s no robots, googlebot, etc meta tags in the source that I can see, and no nofollow apart from on a few things like feeds.

        Also, I’m sure I’ve seen Lemmy appearing in search results already.

      • Admiral Patrick@dubvee.orgEnglish
        1·
        1 year ago

        Nope, it’s allowed.

        The default robots.txt disallows access to a few paths but not /post or /comment.

        There are lots of crawler bots hitting my instance (ByteSpider being the most aggressive). I just have a list of User Agent regexes I use to block them via Nginx. Some, like Semrush, have IP ranges I can block completely at the firewall (in addition to the UA filters)