https://lemmy.nz/ and https://quokk.au/ are running Anubis, and so those admins may be able to offer insight :)
post
replies:
Sure. I have found that the default botPolicy works fine for blocking the AI bots, but blocks federation.
At the reverse proxy level:
if ($request_method = POST) {
proxy_pass http://nodebb;
}
Because Anubis can't filter by HTTP method, unless I am mistaken. This just broadly allows all incoming activities. If you want to get specific, limit it to your shared inbox or individual user inboxes via regular expression or something. I didn't find that it was necessary.
As for botPolicies.yaml
# Allow /inbox
- name: allow-ap-headers
headers_regex:
Accept: application/ld\+json; profile="https://www.w3.org/ns/activitystreams"
Accept: application/activity\+json
action: ALLOW
- name: allow-assets
path_regex: /assets
action: ALLOW
The former allows those specific AP headers (it is naive, some AP impls. send slight variations of those two headers.
The latter allows our uploads.
replies:
It would be nice to have a much more aggressive anti-bot stance for communities/content that aren't local. If google or any other crawler wants to crawl c/lemmy@lemmy.ml then it should do it on the source instance. Doing it on mine makes no sense.
replies:
replies:
Not Lemmy specific, but I wanted to set up Anubis in a setup where I have one reverse proxy (nginx) handling many different domains. Last time I looked, it seemed to need one Anubis instance per domain. Is that still the case? Goal was to have a single Anubis instance and route all through it
replies:
i think feddit.org and lemmy.dbzer0.com both use it
in feddit.org's case, the anubis loading screen displays for waaay too long. i've told the feddit.org admins repeatedly but got no response.
i'm not sure whether lemmy.dbzer0.com still uses it, but i think i remember seeing the loading screen there too. maybe they just reduced the loading time so much that i can't see it anymore.
replies:
all 16 comments