There's also still some pre-distributed cache legacy issues that we need to look at, like the KillMail calls just giving you an error all the time, except once, every hour, for one application using that specific key.

I assume we'll be seeing CCP Nimbus on IRC aswell?

WOOOOOOO \o/

edit://

All hail the Prism and, uh, the Nimbus?!
I assume we'll be seeing CCP Nimbus on IRC aswell?

In any case, here is a quick list of stuff that should probably be given highest priority:

#1 Cache
#2 ?
#3 ...
#4 profit!

I don't know man. He just managed to forget his forum password and lock his account from the forums.. so maybe IRC is a bit too much to hope for

Sorry Nimbus, I <3 ya, bro.

Hello, I am apparently not so good with computer

Please don't beat me with sticks (or anything, really) just yet... I'm looking forward to getting stuck into this stuff, and yeah, I should be in IRC - assuming I don't do anything stupid with that, too.

<3

Hello, I am apparently not so good with computer

Please don't beat me with sticks (or anything, really) just yet... I'm looking forward to getting stuck into this stuff, and yeah, I should be in IRC - assuming I don't do anything stupid with that, too.

<3

Hello, I am apparently not so good with computer

Please don't beat me with sticks (or anything, really) just yet... I'm looking forward to getting stuck into this stuff, and yeah, I should be in IRC - assuming I don't do anything stupid with that, too.

<3

A way to query blueprint attributes found in personal and corp AssetList calls.

I'm going to sticky this topic here.[/b][/u] If you have any suggestions for something you think we should look at, feel free to provide them here. I'll probably go over it every now and then and delete all the posts. Make some list of stuff I add to the backlog and maybe give you a progress report if I find the fountain of time and suddenly have all the time in the world to work on everything I-¦ve ever wanted.

Could we get some JSON and OAuth

Where the bloody heck is CREST?

Why even bother this dead horse of an API?

I'm also interested to work with CREST;
Where can we find some documentation and info on that subject?

/me thinks the thread is dead :/

My one request for the TODO (I saw this referenced in the OP) is please make it so that I can post my corporation api to multiple killboards, and they can all suck down my corps kills.

Please, oh please add container names to assets api. It would help to solve old problem with multiple starbases located in one system. I will just give towers/silos/harvesters some weird names and modify my utilites accordingly.

Can we get a list of the new error codes and what they mean?
We could find out the hard way, but this is probably a bit easier on both of us.

What happened to https://api.eveonline.com/char/FacWarStats.xml.aspx? ?
If supplied with charid, vcode and keyid this returns a bad request.

This always used to work, until it didn't. Then I spent my whole weeking, pulling my hairs out, finally nailing my bad requests issues down to this idiotic thing. What's up with character FacWarStats?

And here you thought I had forgotten about you!
Fixes
- CharacterID.xml.aspx now supports unicode characters
- ID's that do not have an associated name should no longer create errors on request, be they supplied internally or by user input.
- Missing owner typeIDs have been added to the following pages (this should remove the need to make up to three calls to know wether a given ID is a character, corp or an alliance):
-- char/ContactList.xml.aspx
-- char/MailMessages.xml.aspx
-- char/UpcomingCalendarEvents.xml.aspx
-- char/WalletJournal.xml.aspx
-- char/WalletTransactions.xml.aspx
-- corp/ContactList.xml.aspx
-- corp/WalletJournal.xml.aspx
-- corp/WalletTransactions.xml.aspx

TODO List:
Tech:
CORS
JSON

What error codes? HTTP 403?

We need errors!
/c

You can already get that with the location API call, which gives you the x, y, and z position. You can then look for the nearest moon (moon positions are in the SDE), and you don't even have to name them funny things.

TODO List:

Missing Data
Sovereignty Data
- Indices and such (Not sure Design is cool with that)

Missing Calls
Blueprint Data

This change caused some applications to break, for instance eve-bb. We have been debugging a evebb forum issue and the root cause is the 403 error if a member deletes an API key. This software is expecting the error code in the XML data and a 200 response. A 403 header implies that there is no permission to access the script or the resource, it does not say that the api key was deleted (Which absolutely should stay in the XML response not the HTTP Header)

What error codes? HTTP 403?

We need errors!


/c

With CREST now being demo'd publically, what are the chances maybe we add new things to CREST first get them working then start swinging things over from the current system?

I'd love to be able to get contents from coupling arrays, as well as what recipe is in a given reactor.
Want to add automated alerts if a pos needs to be feed or emptied to continue the reaction(s).

CREST requires people to accept the developers license (as far as I understand it.)

As the developers license hasn't been finalised yet, no releases of authenticated CREST access can be done. Legal issue, rather than technical.

"WONTDO List:
Planetary Interaction API - Data schema simply incompatible with API."

Is there any chance another way for this will be found?

It would be really nice to get automatic data this way.
thank you.

Yeah I'm aware of the mail issue. It really bothers me as well for reasons I don't want to share so that they don't start bothering me even more!

WONTDO List:
Planetary Interaction API - Data schema simply incompatible with API.

PI feels more and more like some fancy toy that had nothing to do with EVE in the first place and that is now left to die...

This is so uncool...

Actually, I think we did pretty good that day with over 800 reads of the first topic which was "The manifesto of a Revolution" .

I don't anticipate a quick jump of membership as so many people don't care about PI what-so-ever. Many do not even consider it a profession. This strikes me funny because it actually involves 2 general types of professions... mining (planets instead of asteroids or ice) and manufacturing (the conversion of p0 to p1 and its subsequent blendings in p2, p3 and p4). Additionally... if you are working... what you work at could be considered your profession... and ask anyone that conducts PI... IT IS WORK (the click fest).

The problem is not that people do not consider PI as a profession.
It's just the clickfest that turn them away.

And because only a small portion of the playerbase actually do PI, CCP has no interest at the moment to fix the API to support PI.

unfortunately, I must report that many have stated to me, especially the day of the forum launch, that "PI is not a profession". as I am not a programmer i can't speak to the api stuff. This being said, i can still talk about what i think should be and how is should be done... hence the forum. maybe you can join the forum and contribute your views and ideas. I have seen your pi planner before and I think it can be of help to those of us in need. I even have a few things i think we could discuss that would utilize your programming talents.



This part, while somewhat true, is just crazy. with PI being so involved in so many things and now with the new mobile structures they have to start putting more attention to those that conduct it.

Noob here, but wouldn't that kill our ability to cache those results? Captain Thunk's suggestion that is. Chances of anyone ever requesting the same as you is near 0 so we cannot really cache it.

Noob here, but wouldn't that kill our ability to cache those results? Captain Thunk's suggestion that is. Chances of anyone ever requesting the same as you is near 0 so we cannot really cache it.

I hate you all very much... as in very very much... as in KAJ GHSBF&P*(UI#WOSDHBUI&*(SEFVDD&*UIFGHIKSDg

http://i.imgur.com/jTWAhjd.png

Please keep in mind this is again just me smashing my face on the keyboard hoping for things to work.

For now it mostly works, I have some more stuff to do on the backend but basically it's a new endpoint: eve/CharacterAffiliation.xml.aspx?ids=

You will notice thats ids, as in plural... as in batch that **** up.

No promises on anything aside from I will continue to work on it and hopefully get it code reviewed and fixed enough for release at some point in the future.

AWESOMEEEEEEEE.....

and now add an indicator on what I've found in the "CharacterID.xml.aspx" API... like don't do characterID when the ID belongs to a corporation...

just my 12.5 cents

I hate myself so much... I went and added the DUST wallet to the corp wallet balance/transaction/journal history API endpoint. Now I gotta go test and I hate testing... damnit... /rage

I hate myself so much...

While you are in guilt phase, could you add container names to existing assets API endpoints? Please do it!

* DUST wallet division added

Is this live now? Or Soon(TM)?

I hate myself so much... I went and added the DUST wallet to the corp wallet balance/transaction/journal history API endpoint. Now I gotta go test and I hate testing... damnit... /rage

Just to get an actual list of changes out since I have been rambling a fair bit (and a dev blog will come later):
* New OwnerID endpoint for looking up names
* DUST wallet division added
* Character affiliations endpoint added that contains slim character info about what corp/alli/faction they are in.
* Added factionName to the corp/CorporationSheet when factionID > 0
* Added contestedAmount to map/FacWarSystem that contains a float from 0 to 1 of the contested percentage

I am also now looking at adding factionID to other missing locations.

Just to be clear, this is all stuff I have done locally but am still waiting on proper code reviews and such before it gets deployed. There will be a dev blog before it's all done so just keep watching for that.

Where the bloody heck is CREST?

Why even bother this dead horse of an API?

This.

Not this.

This.

WONTDO List:
Planetary Interaction API - Data schema simply incompatible with API.

Would you please reconsider your position on this one?

It doesn't have to be complex.

In our case, what would be helpful is knowing what planets a character has command centers, what commodities are being extracted or produced, and the time until those extractors are scheduled to end. Maybe beyond that just a list of assets (commodities) that can be transported to a Customs Office.

This would go a long way toward making it possible for us to create tools that help us keep track of PI installations. On a personal level, we can make sure we're re-installing our extractor programs when they finish. Currently, there is no way to automate this like you would with EveMon and your skill queue. On a group level, such as a corp or alliance, it would help us better manage projects where many people are "chipping in" different commodities toward a common end.

I don't understand what you are saying when you say "data schema incompatible with API." The API outputs XML. What data is not compatible with XML? I can understand that it might be more challenging to represent a complete PI installation in XML, but you are already doing this in your databases or PI wouldn't even exist. But putting that aside, most of us do not need anything that complicated.

With the advent of POCOs, this becomes an even more important aspect of Eve that is missing from the API. You guys have been great at providing us with important data we can use, but this is one area that has been neglected. I did some Googling and this has been asked for since as early as 2011, so it is needed/wanted.

Please reconsider your stance on this.

It doesn't have to be complicated -- some basic data is enough for 95% of the ways in which it would likely be used.

I make ZERO promises, but I will at least talk to CCP PrisimX and see what might possibly be possible. I have no idea, but I will ask some questions.

I make ZERO promises, but I will at least talk to CCP PrisimX and see what might possibly be possible. I have no idea, but I will ask some questions.

Thank you. I can see why the DUST community admires you so much.

I really appreciate your willingness to look into this. Something else crossed my mind after I read your post: there would also be value in being able to query the tax rates and owners of the POCOs for different planets. Perhaps a separate query for planetary information in a solar system? If I could query a system and get a list of planets, their types, and the POCO rates, there is a lot we can do with that.

I donGÇÿt like the idea of querying the API for the owners of customs offices. Why? Just try to imagine how nullsec alliances would react to the proposal to allow API calls for who has got a POS on some moon. This would be free and very convenient intel for everybody who is interested in "acquiring" this spot.

I have no problem with other planetary data and tax rates being available via API though.