So I was simply going to port the SC bot over to Mastodon API. But smallwhite's suggestion of combining challenge bots into a generically maintained bot, and also data input points not reliant on a commercial or single source. So I'm starting this thread to gather ideas about what this type of bot might look like. Feel free to join the discussion, both technical and non-technical views are welcome.
My thinking is the "bot" would have the following features/design.
A database (MySQL or PostgreSQL) which would have the following things:
- A Challenge Metadata set of tables, which would allow the input of things like,
-- input locations: email, webpage, Mastodon keys, WhatsApp phone number, etc.
-- A definition of the challenge scoring system.
-- A definition of the challenge display system (webpage, embedded chart).
-- Challenge dates, e.g. start and end dates.
-- Challenge controls, crontab type data, how frequently to poll data sources, etc.
- User data area, name, nickname, email address, WhatsApp phone number, Mastodon nickname, etc.
- Lookups area. Language names and ISO codes, Language families and ISO codes,
- Data area which will contain the actions users have taken, read X books, wrote Y words, studied Z hours, etc.
After we get a fair definition I'm happy to open a github repository and add it into the language group (where we keep our version of PhpBB, the current SuperChallenge bot, etc)
I don't particularly like the current SC Bot use of stored procedures in MySQL, and I would prefer PostgreSQL, but that is just a personal preference.
It might be useful to create a REST API for the generic bot, so people could develop Android or iPhone apps if they were that way inclined.
**I am aware this isn't really true RFP, but it sounded nice