• Tiff@reddthat.comM
    link
    fedilink
    English
    arrow-up
    5
    ·
    1 month ago

    Possibly, as it’s one generic endpoint, but it also blocked a few other things people in the fediverse created, which are mighty helpful in diagnosis of these and other issues.

    So using some AI model or whatever CF uses is probably not going to be the best thing for us as it classified a POST request as a crawler?? 🤷

    I’d have to whitelist every regular endpoint as well and then it gets messy as CF only gives you so much control as a free user.

    So, for the moment I’ve blocked the most annoying ones based on UserAgent.

    • cranakis@reddthat.com
      link
      fedilink
      English
      arrow-up
      4
      ·
      edit-2
      1 month ago

      I’d have to whitelist every regular endpoint

      That’s why I started with “this might be to much work” 😆. Seems like there would be a way to do it without the automated bot blocking just using allow and deny (or challenge I guess it is here). The list would be a bitch to create by hand but shouldn’t it exist already somewhere in the federation configs? If so you could broadly allow those while blocking or challenging otherwise. I guess it comes down to how do you identify bot traffic with free, without the tool on.

      Full disclosure: I have CF Enterprise experience but I’m just guessing in the Lemmy/federation part and haven’t messed with CF free.