In reply to @skyflare:conduit.rs
Fully justified.

In reply to @skyflare:conduit.rs
What are features that should be added or easy to add in a new bot? (not promising anything ofcourse)

I'm using dictation here so this may read more of a stream of consciousness than usual:

So I've had all this in my mind for a while now but never actually set it out loud to even like jitsi or something and basically my overall recommendation is to focus first on the data structure. So you've said above more about like features and stuff but what the old bots didn't have was the ability to annotate what we'd already had so all we had was games and players and making them together so that meant that when we wanted to we couldn't add like you know a sub game or server address for example.
In my mind it made most sense to consider storing all this data actually purely in the matchmaking channels matrix data because that way the code just operates on what's there and can be hosted anywhere whereas but I guess sqlite would be a perfectly fine substitution for this it just means that only the person hosting the code can actually access the real live data and for example for export or whatever.
This applies even to you know a user a user could have aliases that they get pinged by or you could store you could provide a mechanism for them to store their own time zone in and so that then when you say got match it'll ping everyone with the time that will actually happen in their own time zone but even that to be fair it was a kind of feature that I'm not sure how much will be used.
The matchbot here does definitely seem to be used mainly for I'm ready to play a game now who else is available but if you look in the channel topic you can see we did have detail of people's overall average weekly availability and which is yeah. Wow this really has been a bit of a stream of consciousness I will try to edit it a little bit hopefully it makes a little bit sense and if it doesn't then feel free to suggest a gypsy Meetup and we can hash it over a bit more one-to-one.

the same way we store the data that allows the IRC bridge to use more lines before flooding protection kicks in: https://matrix-org.github.io/matrix-appservice-irc/latest/room_configuration.html

curl $'https://freedombox.emorrp1.name/_matrix/client/r0/rooms/\u0021uagwTOyQbbWrZgwyPO%3Afreedombox.emorrp1.name/state/org.libregaming.bot/supertuxkart' \
  -X 'PUT' \
  -H 'authorization: Bearer XXXXXXXXXXXX' \
  -H 'content-type: application/json' \
  --data-raw '{"alias":["stk"],"server":"play.libregaming.org","players":["@emorrp1:freedombox.emorrp1.name"],"libre":"source contains 2 nonfree karts"}'

In reply to @skyflare:conduit.rs
'"libre":"source contains 2 nonfree karts"' What?