Cool, been playing a while, always ****, great, found out two plays are OP, I might win now!
Narrator: Removed.
Oh *****.
If something needed removing then so be it. It's clearly a data driven decision.
*takes FB out back and shoots him*
With regards to an API, I think it's an excellent idea. I get not wanting to disadvantage non-technical people but from experience, I've found in other games people tend to publicly release their applications. I personally wouldn't; code I write is generally more theoretical (and never fully finished) to learn some more tech in the Java eco-system. It's never as polished as I'd like and tbh nothing I've written is unique to my coding kung-fu, can easily be worked out in spreadsheets - most of my ideas tend to be protoyped in LibreOffice.
Was thinking JSON for language independence but reading about Apache Arrow, it seems impressive for big data. From a Java perspective, examples I've seen don't appear to be as clean as you'd expect from JSON solutions, but then Python is used by hackers ;). Would arrow be appropriate for the use case of you logging in, wanting to download upcoming draft data?
The question is what functionality the api would provide. One game I used to play had a second "shadow" account created. This was read-only in nature, so any apps accessing it couldn't go in and trash the game for you. Another required third party app writers to register and gain a token for data access. Designing a good api is an artform, it should imo follow RESTful guidelines consistenty.
It also bears mentioning that irrespective of a public acing api being available, it'll always be possible to get data by logging in automatically and simulating the request, processing returned data, data a browser would receive.
It's a tough one. Much as I'd love a third party app so could get data, do analytics, send gameplan in would that damage site analytics as now accessing via phone / browser or would a login to the api server count? I suppose that removing the need to log in also loses the social side of things.
EDIT: Noticed earlier reference to a data committee - should the API be part of that or a sub-committee? Not everyone is at the data analysis level of settherick and others, for me data should drive decisions that affect things in game whereas api should foster the environment for people to make tools that can drive analysis, a distinction for me.
Last edited at 10/26/2022 3:22 pm