EVE Information Portal

Kind of agree on this, it's a bit short. I mean writing a working parser for both the XML and CREST Api isn't something you do within a few minutes, that takes some time (and more time debugging it)...

I've got a working XML/CREST Api library lying around I wrote for another project of mine, now I just need an idea -.-

No.

Will the SSO/Oath documentation for non-browser apps be updated within the timeframe of this challenge?

http://eveonline-third-party-documentation.readthedocs.org/en/latest/sso/nonbrowserapps/

@CCP Foxfour

Has the issues with the CREST Location endpoint been fixed, as discussed in this post?

https://forums.eveonline.com/default.aspx?g=posts&m=6274873#post6274873

Because GPL is a nightmare to use on any project that may have some stuff "linked" that you don't want to release.

Some idiot said that *linking* to something makes it a derivative work (RS in fact). Despite the fact that many lawyers have said that it is stupid, (it would be like Britannica claiming copyright on anything that reference their encyclopedia), no one wants to touch it in this context.

So BSD/MIT licenses are preferred were there is some context where some code will never be released (ie eve or some other websites core code) But still you want to release some of it with modifications.

Seriously our lawyers where very much on the idea of either keep it all open, and they meant *everything* and publish it all, or release nothing (GPL does not require you publish any change if you keep it all to your self.) Go to court and probably win after 20Million and a **** ton of bad PR. Or stick to BSD/MIT code. Even LGPL/classpath exception is a bit of pain.

Unfortunately no. :(

Not much we can do to stop this.



I am the only one with the ability to edit the responses. The "worst" someone could do is submit an application under someone elses name... but if the same app gets submitted twice it shouldn't be hard to figure out who the original author is. Especially since I am looking at each one every day. :)




No, you can only win once.



Outside the top 3 they will not be ranked no. I am also not comfortable talking about who the judges will be at this point. Will probably mention it when we publish a dev blog but not right now.



That is basically a line from our lawyers. I am hoping to link to all of the Git repos when done and those do require a license and I believe your name has to be in that. I have no intention of ever mentioning anyones real name or character name. If we ever were to say anything it would only be character names but I fear since we are linking to a Git repo a real name could be figured out. Open to suggestions on how to better handle this.

having a play with the crest stuff atm, interesting learning curve from xml to JSON. pretty much got the public stuff under my belt, tbh documentation is a tad scarce but oh well we engineers never are that good at paperwork !

so now playing with the authetication stuff, so my question is what do I put in the callback URL if I`m writing say a desktop app, err think win10 app, therefore no callback url available, this is proably obvious but I don't seem to be able to figure this point out.

A pseudonym is perfect and I would really recommend people do that if they don't want to link real names to EVE names. I will admit I don't think much about this as I don't care and have linked RL to EVE for a long time. So hearing other people talk about this stuff is always interesting to me.

That would be choice of super capital skin from the NES sorry.

thank you for the helpful replies, it is appreciated.

I don't want to derail the contest thread as I think it is a really good idea to push the crest functionality and has pushed me to try it out, mainly as I really enjoy the XML api, and have learned so many useful real life tradable skills that have helped my day to day job, great to learn stuff from a pastime with data that is complex but understandable from game experience.

I like the way crest is set out and think I may start using JSON instead of XML so cool beans, the crest api is expandable and once over the initial hurdle pretty easy to use, and contains a lot of easy to navigate information.

the one downfall I see from the crest stuff thou is this authentication system effectively meaning anyone wanting to use restricted data in their application would have to effectively run a web server to cope with the authentication system, that is assuming I now understand the call-back system. well great if you application is a web site, not so good if you app is desktop / phone or tablet based. I had a multitude of ideas for a win10 universal apps [I like this platform a lot], but the authentication system seems to negate this use.

so back to my original question, how do I use authenticated crest with no access to a server for the call-back url ?

apologies if this seems like a moan however I am either mssing the point which is quite possible or the authenticated crest is a non starter for apps that don't have a website.