Programming.Dev/p.d-legal
Programming.Dev/p.d-legal
6
2
Fork 3
Code Issues 1 Pull requests 2 Projects Activity

Update stance on autonomous AI agents #38

Open
bugsmith wants to merge 1 commit from bugsmith/p.d-legal:main into main
pull from: bugsmith/p.d-legal:main
merge into: Programming.Dev:main
Conversation 0 Commits 1 Files changed 1 +7 -2
1 changed files with 7 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
content/docs/automation-guidelines.md
View file

@ -24,13 +24,14 @@ Automation should not be used to affect the voting system in the instance. The v
## 2. Bots
These guidelines are specific to bot usage. This means accounts that exist solely to be automated to do things (tldr bot, remindme bot, reply bots, etc.) or that do specific things without any form of human intervention in the chain
These guidelines are specific to bot usage. This means accounts that exist solely to be automated to do things (tldr bot, remindme bot, reply bots, etc.) or that do specific things without any form of human intervention in the chain. This also includes accounts designed to be driven by autonomous artificial intelligence agents.
> Examples of things in this category:
>
> - Automatically posting things from an rss feed
> - Automatically generating tldrs of articles posted to a community
> - Automatically posting a link to an alternate frontend for a site when theres a link to the site
> - Having OpenClaw and similar software act run an account that posts and replies autonomously.
### 2.1. Mark Bots as Bots
@ -50,7 +51,11 @@ Before using a bot in a community allow the mod to opt in to the bots.
If a bot is deemed to be a well behaving bot that brings net good to the instance it can override this rule as long as it has been approved by an admin. If this happens mods should still be able to opt out of use of your bot.
For sites that are not separated into communities (e.g. the main feed of a microblog), you only need mod permission if the account is hosted on the instance.
For sites that are not separated into communities (e.g. the main feed of a microblog), you only need mod permission if the account is hosted on the instance
The account profile of the bot **must** list the communities which have opted in, including the username of the moderator that did so.
UlrikHD commented 2026-03-21 08:47:01 +01:00
Review
Copy link

Personally taste, but I'd probably drop the bold text around "must", the meaning behind the word stays the same, i.e. obligatory to follow.

We also need to take into consideration what effect this statement has on previously established bots that doesn't fulfill this requirement, but that's maybe a discussion to take on discord.

Personally taste, but I'd probably drop the bold text around "must", the meaning behind the word stays the same, i.e. obligatory to follow. We also need to take into consideration what effect this statement has on previously established bots that doesn't fulfill this requirement, but that's maybe a discussion to take on discord.
For accounts hosted on this instance, the previous point also extends to externally hosted communities.
UlrikHD commented 2026-03-21 08:51:30 +01:00
Review
Copy link

This is a confusing statement, I don't see anywhere it say that federated bots are treated differently, so what does it mean that local bot have the previous points extended to externally hosted communities?

This is a confusing statement, I don't see anywhere it say that federated bots are treated differently, so what does it mean that local bot have the previous points extended to externally hosted communities?
bugsmith commented 2026-03-21 09:14:45 +01:00
Review
Copy link

Perhaps it needs rewording.

Federated bots have to follow our rules when they interact with our coms.

What I'm trying to say is that accounts hosted on our instance must follow the rules about listing approval from mods even when they interact with coms hosted externally.

I guess it's redundant when all our rules apply to accounts on the instance, but I wanted to make it explicit that they must also seek and list approval.

Perhaps it needs rewording. Federated bots have to follow our rules when they interact with our coms. What I'm trying to say is that accounts hosted on our instance must follow the rules about listing approval from mods even when they interact with coms hosted externally. I guess it's redundant when all our rules apply to accounts on the instance, but I wanted to make it explicit that they must also seek and list approval.
## 3. Tools