EVE Technology Lab

Right now:

1. MemberTracking have two usage variants: with and without "extended=1" parameter that adds all details of member like what ship he is in, what location, when did he last logged off and logged on, his roles etc....
2. Current timer for Cache is 6 hours which seems fine for just accessing member list where You dont excpect tons of really important changes between chache timers - a member might joined, a member might left - but overall this data is static
3. If You use "extended=1" You start to get information that provide value if could be tracked in shorter periods:


• Login/Logoff times when served once every six hours can be used only to veeerrry roughly determine the time a member spends in game - basically at which TimeZone but not precisly what hours
• Location - like above - You can see basically when he is at a snapshot or where he logged off depending if he was online or offline at that time - You can really say if he is spending more time in home system area (null or wh for example) or farming in hi-sec

What would we get if the timer for the MemberTracking API was reduced:

1. More insight into time spend in game by our member, this can be used to, for example:


• Spy/Theft suspects reduction
• Planning ops based on players counts in different hours
• Cool corp activity graphs


2. More insight into type of activities members perform:


• Does the member spend more time in pve ship or mining ships or pvp ships
• Does the member spend more time in home are roaming or maybe he is sitting in hi-sec in a Golem
• Where does members spend most time in - what systems and how this changes over time within a timezone
• Which players ignores CTA or just show up for a moment only to get back to minng after hour
• Again - cool corp activities geographical mapping

So what would I would like is the reduction of cache time on MemberTracking API from 6h to 1h tops if not even shorter (10 minutes anyone?? no?) At least for "extended=1" version.

I dont know how CPU intense is getting this data but my guess is that its not big.

This let me check ship locations but not who sits i them - am I right? And from the two points I showed up the login time is the one I'm most interested in closely followed player location

Edit: I derped - anyway - this requires getting api from everyone - which is doable but its something I would like to not have to do. Its tedious and annoying both for directors and for member.

Hmmmmm I can see where this would be usefull. I will have to do some research on how badly this will effect us, but do not see a design reason not to.

Would just like to chime in that it would be cool to have this. Those graphs on player info would be really cool. I collect full API keys from all my corp members anyway (for security reasons), so this might be neat to do now.....


This is just my own speculation, but given the number of active player corporations, if EVERY corp uses it (unlikely), it should be a max of ~290k requests per timer (evewho has that many corps listed). I can see why the timer is so long then, but that still seems, if i recall correctly, like a drop in the bucket in comparison to, say, the KM endpoint numbers you showed at FF this year. This could be exciting.

Not yet, been to busy with other stuff sorry. :(

While we're at it ... when (and why) has Member Tracking moved from /char/ to /corp/?

I was getting 400 - Bad Request HTTP errors and hunted my code up and down until I finally recognized that change.

When You do find time to do it I have another request that will probably be turned down, as this information is not strictly available in client via corp menu but if i recall is available for each player sepearatly (so probably corp api is not place for it but would be great if provided for corp/members)

Anyway: ship ID of the ship player is in and/or name of that ship exposed trough members API.

What would it be good for? Two uses for this data:
1. looking for certain ship that is reported stolen
2. looking for certain ship that is borrowed by someone but a player dont remember who that was so You can check.

Tracing the route of a single ship, who is using it, how it was renamed, between members api and assets api and IGB http headers