ArieThere's also a queues endpoint which gets polled once a minute. It appears to return a list of all matches ever played and all the players in those matches and the pug histories of those players. While it probably just should return the current queues.
http://fakkelbrigade.eu/i/1686908740.jpg
So that's become a 1.7MiB JSON with 80k lines. It gets loaded 5 times after opening the site.
If you compare the two endpoints 'https://rglpug-api.tf.plus/api/queues' and 'https://rglpug-api.tf.plus/api/queueEvents' they are the same responses, except queueEvents is responding an infinite amount of times with the data stream of 'queues' as its messages. So its pulling that 80k line json file every second.
Presumably this is so that the client is updated to match the server but the client itself should handle its own update requests when needed. Also, having a front facing API that just spews data seems like it would be incredibly expensive lol.