welcome back!!
couple thoughts:
Try not to use Bootstrap!
are you thinking of using something else for components and styling? i would worry that tossing on too much change from your norm might end up causing burnout or issues for you in development; though i think my concerns would moreso be if you wanted to roll everything from scratch... if you have just a different flavor of components and stuff it's probably a no brainer.
TG Forum OAuth
using forums auth is really nice because you can get the user groups, this is what powers stuff in scrubby to know who is an admin and who isn't, and mso is gonna use it for provisioning access to tgs panels on tgs5 servers soon
MSO can we have the user’s avatar URL in the OAuth response?
i'm pretty sure you can already get the avatar from the oauth response, it's included when you include the user details scope (
details in the thread here)
Cache and expose round info with an API
one thing that would help a ton though i don't think it is stored in the db is if we could have an api that resolves a round id to a file path, i have this relation stored in scrubby but it only exists from crawling the /tg/station website... we should see if maybe that's something mso could provide even...
one thing that im just thinking now actually is that maybe we should use statbus as a way to provide a set of apis for /tg/ data in general, because one thing that i think would be a really useful api endpoint to have would be the admin roster. i used to get it from statbus parsed from the html of the page you had, but a json response would be a gazillion times better and could be cached and stuff... (this admittedly may fall under what you already planned by "Cache and expose round info with an API")
Previously, stats were generated dynamically, on request when you viewed a page. This was ultimately always a pain in the ass to collate and probably should be handled differently. So this time around, we’re going to periodically (daily?) copy down the most recent stats from the game DB and compile statistics.
this is a better approach not only for the fact that you do it less, but also
you can do more!! with this approach you can do stats jobs that take a longer time to run which you could never provide on the fly but then provide it on a daily basis or hourly basis etc... very cool things could come from that!!
best wishes and seasons greetings,
bobbah 'bee' brown
The information contained in this post is intended only for the individual or entity to whom it is addressed. Its contents (including any attachments) may contain confidential and/or privileged information. If you are not an intended recipient, you may not use, disclose, disseminate, copy or print its contents. If you received this post in error, please notify the sender by reply post and delete and destroy the message.
L’information contenue dans ce message est destinée exclusivement aux personnes ou aux entités auxquelles le message est adressé. Le contenu de ce message (y compris toute pièce jointe) peut renfermer de l’information confidentielle et / ou privilégiée. Si ce message ne vous est pas destiné, vous ne pouvez utiliser, divulguer, diffuser, copier ou imprimer son contenu. Si vous avez reçu ce message par erreur, veuillez aviser l’expéditeur en lui faisant parvenir une réponse. De plus, veuillez supprimer et détruire le message.