I'll admit I'm out of my comfort zone with thus, but I agree the game needs better social tools. Happy (and better) for it to be in game, but if not maybe someone from the community develop it
To set the scene, is this API going to be into a FD server to get information, or into the ED application running on your PC, or simply data dropped/exposed by ED (eg: when you enter a system and/or dock at a station)?
Sorry if this is stupid question. But I think it might be useful to set the scene of how/where this data can be obtain from?
I understand the former is the most powerful, but surely the last thing FD want is millions of HTTP requests spamming them every hour?
Yes this is an important point. I would suggest to have both, but for different information:
- Web-based for semi-static information, such as systems, stations, star coordinates and such
- Client-based for the player's information. I like the idea of a local daemon (HTTP, UDP, whatever) to allow the development of local tools or interfaces
Security is a concern if you use a web-api for a player's information, particularly if you use ED store credentials to authenticate. Hence, local client.
Indeed - https://forums.frontier.co.uk/showthread.php?t=99437&p=1545056&viewfull=1#post1545056Michael,
Can we clarify if you mean an API hooked into the client, or an API on the webserver?
Personally I'm wary of anyone collecting via an API any data outside of the system they are in, or any data that their commander doesn't actually know of.
I think for anything I want to make the data exposed in the companion app's /profile call is plenty. Although I don't think coordinates are included in that, there's lots of guys that would current system coords handy