this post was submitted on 04 Aug 2023
1 points (100.0% liked)

Beehaw Support

2796 readers
1 users here now

Support and meta community for Beehaw. Ask your questions about the community, technical issues, and other such things here.

A brief FAQ for lurkers and new users can be found here.

Our September 2024 financial update is here.

For a refresher on our philosophy, see also What is Beehaw?, The spirit of the rules, and Beehaw is a Community

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

if you can see this, it's up  

founded 2 years ago
MODERATORS
Zmodem@beehaw.org
Gaywallet@beehaw.org
alyaza@beehaw.org
Lionir@beehaw.org
Penguincoder@beehaw.org
remington@beehaw.org
1
The rules for bots (docs.beehaw.org)
submitted 1 year ago by Lionir@beehaw.org to c/support@beehaw.org
10 comments fedilink hide all child comments
 

After some discussions in !chat, we came up with the conclusion we should adopt rules surrounding bots.

We'll ban bots which we are aware of that currently don't follow these rules and contact their creators. Please report bots that don't follow these.

you are viewing a single comment's thread
view the rest of the comments
[–] GeneralRetreat@beehaw.org 1 points 1 year ago* (last edited 1 year ago)

I'd just suggest that this is a defacto ban based on the current requirements.

If bots are going to be command triggered and require pre-approval by individual community moderators, I think it would be prudent to include an index of registered bots + commands in the community info pages.

Currently I can't think of any reasonable way for a Beehaw user to know which bots are operational and what their commands are. If bots need to be command triggered but there's no way to find out which ones are functional, why approve them to begin with?