Since the Keychain.list is rate-limited now, its very hard to find out if you have access to stations or not.

Could we add a new function to Keychain to get a full table of the access? This would be not much load (theoretically, since its one simple select with a few, if any, joins) on the DB side and not overload it like before with too many calls. Then we can deal with the table our self in LUA and offload the handling of the keys to the client.

Also a new sorting for keys would be good. Station access keys on the top and capship sorted lower.

+1 Fetching keys in bulk would be awesome (all keys and their access data in one request).

Additionally it would be cool, if the fetch could be made with a filter option "modified after <TIMESTAMP>". This would make updating the key list (in plugin) a little smarter.

--
Lanigiro Elbbarcs

So, we aren't against the idea of adding this kind of feature, although it requires some additional thinking on our end.

But, resolving the actual intended purpose might be a better solution than some kind of API. Like, just.. letting you see what stations and content you have access to, and sending that data on player login.

New API calls to service interesting plugins are.. useful. But more-useful is just resolving the common case so that people don't even need plugins.

Sounds good! Thanks for taking this into your todo list :)

Well, cool. But more to where I was going in my response.. I guess it might be valuable for a more specific run-down of exactly what people would like to conveniently do and see within the key interface, so we can focus on delivering that.

It would also be good for Owners of a key to see who gave/revoked keys. Like a history of all actions.

Of course, that would be the right thing to do.

Well, here's one more feature request to the new key interface. Players would like to manage users by copying them from another keys (one by one, or multiple users once (ctrl-select) or all users).

(This topic starts to go off-topic, sry)