Errbot VS blossom

This reminds me of a time 10 years ago when the company IRC channel had a bot that was able to interpret python and output the result. We got nerd-sniped for a few hours trying to make the bot interpret its own output as input again. Fun times.

This ChatGPT thing looks like a box that has been opened and cannot be closed again.

Btw, that chatbot from my anecdote eventually evolved into errbot. https://github.com/errbotio/errbot

So I started working on a bot that would live in modchat, able to help us with whatever we needed and something that could be extended in the future. (For those interested in the tech side of things, we originally started by building on the errbot platform before eventually building a brand new system from scratch that better fit our needs.) As we built, we needed a name for the new bot; a few different names got thrown around, but we eventually settled on Bubbles.

Interesting Project.

I'm sure you're aware of Errbot (https://github.com/errbotio/errbot), though not specifically designed with slack in mind: I have had excellent success with this framework.

How does slack-machine compare?

PS: Please forgive the naive question, I'm about the board a flight and don't see anything mentioned or anything radically different about the stated goals.

Some limitations: if I'm on the tramway I'd like to send a Telegram message to my bot, but when I'm on a terminal, maybe I'd prefer to interact using IRC or Slack, if I'm in front of my desktop. Six years ago somebody asked about this in the Google+ group (now disappeared) and later somebody asked for this in the GitHub issues forum Support multiple backends in one instance #1137. But no advances on this matter appeared.

When looking at the API, the way we get all of the information we need, we have access to a fairly large amount of information. The Developer Platform, while it has its uses, is not designed with large and busy bots in mind. It's much better suited for entry-level 'learning to code' style bots that we see frequently pop up on the site. Issues from data usage limits, data storage limits (500kb! Our database in Blossom is over 1.4GB), connecting to services outside reddit (which we have gotten special permissions for, I'll give them that), and more plague the development experience at the time of this writing.

u/goldieczr here's the repo for our primary site, data storage, and API. Python / Django. https://github.com/grafeasGroup/blossom

Really, there was only one choice, and Blossom was brought to life. As the leader of the trio, it just made sense.

In software development, tooling refers to programs or scripts that only serve to maintain other programs or scripts. In our case, we write tooling for the QA and Engagment teams so that they can directly interact with the keeper of data, Blossom, or various spreadsheets that are used to keep track of different things (like the delightfully awesome Treasure Hunts in Discord).