ok botting rules (subject to change, but effective immediately)
bots must be clearly labelled as such, and link to the maintainer’s account in the bio or something. in the future, there might be a bot label.
bots may not perform social actions such as: following, liking, reposting
bots may not post individual posts automatically, with the exception of “daily/weekly/monthly x” accounts, which can post a maximum of one post per day at a fixed time.
bots may not reply to posts/comments unless explicitly triggered:
bots must be triggered by @ mentions, or wall comments on the bot account’s wall.
bots should use the wasteof2 api (api.wasteof.money), as the beta api is subject to change and is designed for internal usage
bots should not poll my server too hard, try using the socket.io api to only perform actions once a mention message is received.
to do this, use a server side socket.io client, and listen for
updateMessageCountevents. when the count increases, request the unread message list and respond to new mention comments.
it is really cool to see all the unique ways that the api is being used, but let’s try to keep it a little bit controlled. :)
comments
well they can but no spamming it/keep editing one, because the revision history blows up and then it's too big
pretty much
the only rule i’m confused about is the last one, since the bot sends more than one message whenever a new turn starts
Also do responses to a bots post count, because that sends a notification to the bot, and would be a bit of a pain to filter for.
are bots in /chat allowed? (someone else has made one, and it responds to mentions, but it also breaks bot rules by responding to /)
and someone else also says that it breaks bot rules because it does not respond to actions that send a wasteof message, because of
bots should not poll my server too hard, try using the socket.io api to only perform actions once a mention message is received. to do this, use a server side socket.io client, and listen for updateMessageCount events. when the count increases, request the unread message list and respond to new mention comments.
chat bots are fine-ish. just make it respond only to slash commands, eg. if your bot generated random numbers, respond to /random 1-10 or something
bots must be triggered by @ mentions, or wall comments on the bot account’s wall.
well how would chat bots work
you modified it so that mee6 fits the rules. Why isn't it unbanned yet?
i can unban the mee6 account if you want. is it polling for changes, or is it using the socket.io for message count updates? i do not think the whole linking stuff would follow that model.
I have deleted the original code for MEE6 and it's only going to be a new concept that follows the rules. Please unban it
What if we want to create a bridge, such as a twitter → wasteof or wasteof → mastodon?
A related question, but can I bridge an IRC server to the chat in here?
if you want sure. just if its bidirectional, please prefix your messages in a way that makes it clear what the nickname of the sender is. (eg. “[jeffalo]: hello world“)
is it okay if the bot edits a post when triggered on the bot’s wall?
oh thanks, also questions:
Also how to use socketio websocket client events in node
Would it make sense for bots to also be able to read their wall posts because that emits a message.
Can real people sign on to bot accounts and post posts?
adding on to the last question, what counts as a “bot account”
Alright i figured out 1, but might I ask that the event for new message includes the message content and id and whatnot pls, that would make it much easier to use, and removes the need to check messages when you get a new one
unfortunately that would not be possible under the current architecture. but a specific mention event might still be possible.
yeah bots can read their own wall comments as triggers. that is fine.
real people can use bot accounts but it should be clear what the human is and what the bot is.
a bot account is any account controlled by automated software
So I can’t have some python script running that post every 24 hours for @holidaysbot
well, there goes my plan to port nihonium to wasteof by forking the code, changing the urls, and debugging
the plan was to scrape the dash for commands
posts would get on the dash by having nihonium follow people who ping it
also it wouldn't use the api at all because it’d be a fork of regular nihonium, which doesn't use an api on account of the tbgs not having an api
Also, since you’re accessing the wasteof API anyway, you don’t need to scrape the page