2 of 101 min

What this project is really made of

From the outside it looks simple: a chat, a bot, replies. But in fact this project is built as a system of several layers.

The first layer is the Telegram interface: messages, commands, media, entry points and the interaction with people itself.

The second layer is the SQLite database. It stores messages, users, profiles, evidence, media and service state. Otherwise the bot would remain a creature with a memory one chat window long.

The third layer is context logic. The bot relies not only on the last message but on the history of communication, the person’s profile, previous reactions, internal rules and accumulated material.

The fourth layer is profiling. The project gradually gathers a structure of observations about users: what they feel close to, how they speak, which motives recur. Thanks to this, replies become less random and more personal.

The fifth layer is work with media material. The bot doesn’t only talk, it also takes part in recirculating content: it returns old files to the stream, links them to the conversation and doesn’t let material vanish after publication.

And finally there are background processes: updating profiles, rotating content, service states, separate cycles that keep the whole system alive.

So it’s more accurate to say this: I made not just a Telegram bot but an environment that connects memory, profile, context, a media library and the logic of bringing material back to life.

Series contents
  1. How the idea of a book gave rise to a space for memory, conversation and recirculation
  2. What this project is really made of
  3. Memory, profile and context: what the bot rests on
  4. The logic by which the bot answers people
  5. How I made a system that doesn't let content vanish
  6. How the project's philosophy is sewn into the code
  7. Why this project lives not only in text
  8. How the bot gathers and updates people's profiles
  9. How I protect the project from chaos, duplicates and chance
  10. Why I wrote this code not for the sake of automation