• JackbyDev
    link
    fedilink
    English
    arrow-up
    2
    ·
    7 hours ago

    Those subdomains are not managed or controlled by the registrar

    I might be getting the terminology wrong, I’ve not had to work too closely with the specifics of subdomains in my career, lol. But you can definitely have blah.itch.io points to a different IP than itch.io and that’s done through DNS. So if they suspected blah.itch.io to be a phishing site imitating Funko’s site, it makes sense that they’d report it to the people controlling that.

    And yeah, it looks like Itch does use sub domains for user pages instead of URL paths. https://xk.itch.io/ So if some user’s page was trying to imitate Funk’s site then I could see this line of thought. I’d need to see the page that was supposedly imitating and what it was imitating to really make a judgement call though.

    • RunawayFixer@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      5 hours ago

      If it had been phishing, then going to the registrar would have been the right call, because you want to take that down asap. But according to itch.io it wasn’t, instead it was a a real fansite that was linking to the real website of funko’s game (according to itch.io). Something which most media companies allow since it’s basically free publicity and goodwill, but if they did want it taken down for copyright reasons, then a DMCA takedown request send to itch.io would have been the correct first action.

      In the response statement by Brandshield, Brandshield does not deny having send a takedown request for phishing to the registrar (confirming that they did), nor do they dispute itch.io’s statement that it wasn’t a phishing site (confirming that they know that it wasn’t), instead they only speak about “infringement”.

      So now we know that Brandshield is knowingly making false accusations that have potentially serious consequences for their victims. And it’s not going to be the first time that they’ve done this, but even this high publicity case will probably not have any legal consequences for brandshield, so it looks like they will continue getting away with it. Unfortunately they’re not alone, it often seems like the entire DMCA industry is rotten.

      • JackbyDev
        link
        fedilink
        English
        arrow-up
        2
        ·
        5 hours ago

        So now we know that Brandshield is knowingly making false accusations that have potentially serious consequences for their victims.

        They said their platform is “AI driven” which could very easily imply this was an automated process with no human making a decision. It’s still bad, but a different kind of bad than “knowingly” making a decision.

        • RunawayFixer@lemmy.world
          link
          fedilink
          English
          arrow-up
          2
          ·
          5 hours ago

          You can’t create an automated machine, let it run loose without supervision and then claim to not be responsible for what the machine does.

          Maybe just maybe this was the very first instance of their ai malfunctioning (which I don’t believe for a second), in which case the correct response of Brandshield would have been to announce that they would temporarily suspend the activities of this particular program & promise to implement improvements so that it would not happen again. Brandshield has done neither of these, which tells me that it’s not the first time and also that Brandshield has no intention of preventing it from happening again in the future.

          • JackbyDev
            link
            fedilink
            English
            arrow-up
            1
            ·
            32 minutes ago

            I’m not trying to exonerate them of any blame, I’m just saying “knowingly” implies a human looking at something and making a decision as opposed to a machine making a mistake.

    • dezmd@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      6 hours ago

      Registrar is 1API.NET which uses Verisign.

      DNS is currently configured to cloudflare (maybe as a result of this fubar scenario?). blah.itch.io would be pointed in DNS not from the TLD registrar in this scenario.

      Contacting itch.io directly would be the first step long before going the registrar route as they obviously manage DNS on their end and not the registrar end.