this post was submitted on 03 Aug 2023
67 points (100.0% liked)
Chat
7498 readers
6 users here now
Relaxed section for discussion and debate that doesn't fit anywhere else. Whether it's advice, how your week is going, a link that's at the back of your mind, or something like that, it can likely go here.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
These rules seem great honestly. The main bot that comes to mind is the TL;DR bot, which one could easily prompt for in a post if they want a TL;DR, if those communities want to enable it for that specific community. Eventually, a list of promptable bots could pop up in one of the instances so that people know which bots are available to be prompted. Alternatively, someone could make a website to list them or something. I can see there being a healthy bot ecosystem forming based on people's needs.
Since we have more control over the source code, I think eventually what would be nice are community plugins to replace some of the functionality of these bots. For example, a plugin could de-AMP a link, or could provide a banner indicating the rules on a post. If someone really wanted to, they could make a plugin to auto-generate summaries of articles too and include it somewhere in the UI. Since these rules are for Beehaw specifically, I don't think bots which create new posts are that relevant, since there aren't really any niche-specific communities (like a bot which posts changelogs for a game or something), just broad communities.
Any bots not clearly labelled as bots should be given a warning, then banned from the instance in my opinion. The bot setting exists for a reason, bypassing it indicates that the bot author is not willing to respect the rules of the communities the bot is posting in.