-> bots typically have 0

Some kind of login system. Not sure if I want an actual login with user/pw or use oauth from somewehre else. Both need effort.

Add things like

• Following count
• channel blurb contains "bot"
• follows channel given as typical channel

Bots that are multi channel don't have a publicly displayed channel (it wouldn't be fair to show one). Thus corrections that just add a channel should be rejected.

Lookup bots by channel (?channel= for check?)

https://api.deepbot.tv/web/streamlist.php

Instead figure out some system where types declare their crawler and potential arguments.

At least define the base URL in one central place.

Already tried it. Got confused as hell. That upgrading guide isn't too helpful, tbh.
http://www.slimframework.com/docs/start/upgrade.html

Let's wait for an update to mini, maybe I'll understand then...

Also consider using a SASS middleware.

Optionally allow the specification of a channel. Especially useful for types without multichannel (honor that in submission from?).

Make it easy to identify a bot of having an existing type or add specify a new type,

To avoid breaking the site if many submissions are added between two runs. Also make sure lock is never disengaged.

Some bot types have known behaviour patterns. Add a twitch bot that tries to verify those for submissions. Some examples:

• DeepBot will always reply to !bot with the DeepBot version and info
• TwitchToken Bot will by default reply to !tokens with the requester's username and a number.
• Nerdbot defaults to !points
• ModBot replies to !modbot/!bot/!botinfo

Think of some way to make it clear this is a verification bot. Should wait for result from #22 before joining chats.

Depends on #21 : check when a bot is in the channel and note that in the submissions list. (Using the tmi endpoint).

Prevent corrections with custom type (0) that already exist in excatly the same state.

Add a field to the submit form and make some of the fields pre-fillable.

The pajbot crawler gets the pajbot channel name instead of the actual twitch channel name. Sometimes they match up sometimes they don't.

Such corrections should be rejected with "The correction was not saved, as it did not hold any relevant changes".

Make sure API doesn't return channel for multichannel bots.
Further don't pass the channel to the correction interface, so it's not publicly visible anymore.

Make it possible to prove channel ownership by setting some data?

use getOffset in the web views. Also add a total property with the total amount of results for a query. (maybe not for the bot/?bots= one?)

The API should also contain direct links to the human readable version of bots and types.

Have a cron job that purges bots that were deleted every so often, by checking the channel API from twitch.

Probably have to add a field to bots and make lastUpdated manually set. Also need to make sure the new field doesn't get exposed anywhere.

Maybe the submitform works without js.

https://github.com/slimphp-api/slim-json

Set the env to production only for twitchbots.info. Also don't send HSTS in non-prod and add some CSPs in prod.

Preparing a statement with infinite placeholders is no good.

check if a bot has already been submitted (and has a type).

This goes with #23, where an IRC client is needed to perform the operation:
Connect to IRC and send .mods instead of using the twitchstuff mods API.

Only for the bot, and the channel may not be a bot.

why, content, affiliation, author, donations?

With columns name, multi-channel and bot count.

From what I've seen you just try to load the template with twig and if an exception occurs it's invalid \o/.

Allow multiple submissions per username with a predefined type (what about corrections?). Only one with a new one. Consolidate submissions and corrections of the same username.