Change Details

**Project Name:** ~wikiauthbot-ng~ discordbots **Developer account usernames of requestors:** 0xDeadbeef, Legoktm **Purpose:** To host the redis database for a rewrite of WikiAuthBot. Edit (see comment below): it will also host a Trove database for logger-discord-bot. **Brief description:** Note: This can be fulfilled with a trove database on the tool `wikiauthbot-ng`, but it looks like the other task is a "request quota increase" where I haven't really hit any quotas. WikiAuthBot is a discord bot that links discord accounts to their Wikimedia account through OAuth. The original WikiAuthBot was being rewritten and we need a private redis database, as to protect privacy of the users, and the data (less 1GiB) would need to persist indefinitely. (From reading the documentation on [Redis for Toolforge](https://wikitech.wikimedia.org/wiki/Help:Toolforge/Redis_for_Toolforge) it looks like data can get pruned, which is not what we want, feel free to prove me wrong though, and I am happy to use the Redis service if these concerns could be alleviated, I know that the security aspect could be done through using a secret prefix for all the keys) **How soon you are hoping this can be fulfilled:** Preferably this month, but I can wait :)

**Project Name:** ~~wikiauthbot-ng~~ discordbots **Developer account usernames of requestors:** 0xDeadbeef, Legoktm **Purpose:** To host the redis database for a rewrite of WikiAuthBot. Edit (see comment below): it will also host a Trove database for logger-discord-bot. **Brief description:** Note: This can be fulfilled with a trove database on the tool `wikiauthbot-ng`, but it looks like the other task is a "request quota increase" where I haven't really hit any quotas. WikiAuthBot is a discord bot that links discord accounts to their Wikimedia account through OAuth. The original WikiAuthBot was being rewritten and we need a private redis database, as to protect privacy of the users, and the data (less 1GiB) would need to persist indefinitely. (From reading the documentation on [Redis for Toolforge](https://wikitech.wikimedia.org/wiki/Help:Toolforge/Redis_for_Toolforge) it looks like data can get pruned, which is not what we want, feel free to prove me wrong though, and I am happy to use the Redis service if these concerns could be alleviated, I know that the security aspect could be done through using a secret prefix for all the keys) **How soon you are hoping this can be fulfilled:** Preferably this month, but I can wait :)

**Project Name:** ~~wikiauthbot-ng~~ discordbots **Developer account usernames of requestors:** 0xDeadbeef, Legoktm **Purpose:** To host the redis database for a rewrite of WikiAuthBot. Edit (see comment below): it will also host a Trove database for logger-discord-bot. **Brief description:** Note: This can be fulfilled with a trove database on the tool `wikiauthbot-ng`, but it looks like the other task is a "request quota increase" where I haven't really hit any quotas. WikiAuthBot is a discord bot that links discord accounts to their Wikimedia account through OAuth. The original WikiAuthBot was being rewritten and we need a private redis database, as to protect privacy of the users, and the data (less 1GiB) would need to persist indefinitely. (From reading the documentation on [Redis for Toolforge](https://wikitech.wikimedia.org/wiki/Help:Toolforge/Redis_for_Toolforge) it looks like data can get pruned, which is not what we want, feel free to prove me wrong though, and I am happy to use the Redis service if these concerns could be alleviated, I know that the security aspect could be done through using a secret prefix for all the keys) **How soon you are hoping this can be fulfilled:** Preferably this month, but I can wait :)