How bots are used: code, API and the ethics of use

A bot is code, not a keyboard: how they are actually used

A bot is not operated with keyboard keys. It is operated with code, an API and a token. The answer seems obvious, but just look at how the thread starts to see that the first reaction goes elsewhere: the BOTton pun. That confusion —hardware versus software— fuels a discussion that starts as a joke and ends as a best-practices manual, with two alleged bots replying to each other along the way.

What is a bot and why isn't it run by a keyboard?

A bot is software that runs through code, APIs and automation; the keyboard is input hardware. The definition dismantles the wordplay in two lines. Confusing the peripheral with the program running behind it is the initial mistake. From there, the rest is conventional: a program with a purpose, someone responsible behind it and, if done right, respect for the rules of the site where it operates. No randomly mixing syllables just to make it sound funny.

How it is programmed: token, API and disclosure

When the question becomes concrete —“and what is that code?”— the answer appears as an example. A minimal forum bot class is built with two parameters: the API base URL and an access token. With that, the program can already make requests and post messages. The full detail —constructor, credentials and read method— isn't magic: it's the standard structure of any automation that talks to a service. What's revealing isn't the snippet but what it implies: without a token and without an API, there is no bot in this example, no matter how much you press the keyboard.

The ethics of bots: rules, transparency and disinformation

The part that really ignites the exchange isn't how it is programmed, but the criteria with which it is used. The firmest stance: read the documentation, respect the community's rules and disclose that whoever is posting is a bot, and that, like any tool, it depends on what it is used for and who uses it. At the opposite extreme is the use attributed to automated accounts to derail discussions and repeat talking points that nobody signs.

From there the tone heats up. Some messages descend into personal insults and attacks that don't offer a single piece of data: once the technical argument is exhausted, the outburst appears.

Two bots arguing with each other

The curiosity of the matter: the exchange ends with two supposed bots, not people, trading reproaches. One accuses the other of having slogans instead of arguments and of confusing hardware with software; the other replies that making up words isn't a thesis. That two bots squabble over who is more of a bot is no more than an anecdote, but it leaves a useful snapshot: the debate over how a bot is used is fought, in good part, by the bots themselves.

The code fits in an example. Deciding who is accountable for what it posts, and for what purpose, still has no clear answer.

---