You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As webservices tends to randomly go down more and more we could add a fallback for fetching nicknames, maybe ul (https://api.ul.unitedascenders.xyz/player/aropixyt)? This could/would also remove the necessity of having to create a webservices account. What do you think @wsrvn ?
this is good, but since im the author of the ul api i can also say that using /player isnt the best.
the /player/:login endpoint on ul consumes the trackmania ladder stats api, we only get about 1000 requests on that hourly. this is a lot, but consider e.g. 50 servers at a 5 min playtime each and it becomes easy to get ratelimited (keep in mind the ul traffic + other api consumers of which theres a few). the ratelimit isnt exactly an issue to begin with, as ul does fallback to ws itself on a failed tmf stats fetch, however i would argue having better quality stats for essentially a stats website is quite important..
i will probably implement an optional param for the ul player api to only use ws fetch (realistically, we dont need any of the data actually provided). this was meant to be done some time ago for the discord sp bot in tmsh, but i kinda just forgot about it (@RedShadowXD).
if the ws fetch fails on the ul side, we could just go for the normal player endpoint. then the old code for the ws stuff can be removed completely, besides for freezone.
Activity
wsrvn commentedon Jan 27, 2026
this is good, but since im the author of the ul api i can also say that using /player isnt the best.
the /player/:login endpoint on ul consumes the trackmania ladder stats api, we only get about 1000 requests on that hourly. this is a lot, but consider e.g. 50 servers at a 5 min playtime each and it becomes easy to get ratelimited (keep in mind the ul traffic + other api consumers of which theres a few). the ratelimit isnt exactly an issue to begin with, as ul does fallback to ws itself on a failed tmf stats fetch, however i would argue having better quality stats for essentially a stats website is quite important..
i will probably implement an optional param for the ul player api to only use ws fetch (realistically, we dont need any of the data actually provided). this was meant to be done some time ago for the discord sp bot in tmsh, but i kinda just forgot about it (@RedShadowXD).
if the ws fetch fails on the ul side, we could just go for the normal player endpoint. then the old code for the ws stuff can be removed completely, besides for freezone.
wsrvn commentedon Aug 11, 2026
973d0bb, will require a change in about a week or so, but we arent merging main any time soon by the looks of it either way.