Characters Security Status Endpoint

[excme]

Feature Request

It would be nice if we could list characters security statuses, 1000 per request. Like Post /characters/affiliation/

Use case

Monitoring characters websites. Now in database have more 17 millions characters. If visitors want to have characters security status cached 1 day - its millions requests to esi via /character/{character_id}

Authentication

A public route, no auth required.

Example return

Propose what an example return might look like. E.g.:

[
  {
    "security_status": 1.24845,
    "character_id": 95538921
  },
  ...999 other characters
]

Checklist

Check all boxes that apply to this issue:

• [x] Feature request description is provided
• [ ] Use case exists
• [x] Feature requires a new route
• [ ] Feature adds data to existing route
• [ ] Feature requires new auth scope
• [ ] Feature can reuse existing scope
• [x] Feature does not require auth
• [ ] Meta feature, applies to all routes

[fuzzysteve]

uhh, why do you need to pull everyone's security status?

[excme]

1. For statistic characters security status
2. For analytics most dangerous characters per day/week/month 2.1. For analytics most dangerous corporations of those characters

[ccee2abf-fb28-497b-88ca-ae3643da4a8f]

uhh, why do you need to pull everyone's security status?

One such usecase would be to determine active players that engage in PVE gameplay.

[fuzzysteve]

It would need to be a long cache time on that, to avoid leakage of information. Yes, when people are active is valuable information. Even active days can be valuable. Automating is potentially troublesome.

I'll admit, I'm not seeing a great deal of value in this. but eh, I'm not CCP.

[jameson2011]

Hate to be the spoiler, but it seems you ask for a denormalised data set. That approach has been quite comprehensively kicked out. For ex: cache inconsistency, CCP's own work in maintaining multiple data sets, so on and so forth.