EVE Technology Lab

Any updates? Just deploying Oauth on its own first and as soon as possible would be great. It will finally give a way to authenticate eve player*. If it would give have access to the classic API as well and not just the CREST API, that would give us a better way to query API keys from users.


*it would allow us to link eve accounts to other forms of authentication.

I am not in a hurry

That's what Crest /may/ be.

It's all about what they decide to open up.

and who you trust with read/write access to your account.

It's been a month - Radio broken?

I think that the issues for CCP when they decide what they want/dare to open isn't 100% down to pure technical stuff and what they can do in a safe manner on their side.

Imagine that CCP opens up to allow us to change skills or market orders or something like that.

Then someone codes a nifty 3:rd party tool to make it real easy for everyone to twiddle their skills or orders or whatever from their phone.

Now imagine that there was a serious flaw in that tool, that for some reason (either by mistake or intentionally ) messed up skills/orders for hundreds of players.

Creating a serious amount of quite angry users.

Is there anyone who thinks that those miffed users would limit themselves to blame the 3:rd party coder (or themselves for trusting him/her/it)?

Of course not, CCP would be flooded in pure vitriol via any channel that is available (and possibly some new ones).

And valid complaints or not, there are lots of more or less serious sites around the world that happily would crank out article after article covering the drama and demanding, or rather DEMANDING!!!, that CCP explains why they allowed such an atrocity to happen.

So I'm afraid that the project that CCP Seagull has been blessed with isn't a very easy one to manoeuvre through either technical or internal policy waters :/

I can't wait to integrate it in Neocom for iOS.

Aiming doesn't guarantee a hit. So keep your hopes down.

The code for it is definitely going out with Retribution, the question is then when we will turn it on for Tranquility. A pretty hefty devblog is written and currently in the publishing pipeline - because this also introduces the new Developer License, and we've had some... issues.. in the past when it comes to that (99 dollars and all that) I want to be pretty careful with this. And then the technical release itself is a pretty serious deal - we don't take giving read/write access to Tranquility lightly.

While I can't promise as usual, as there are factors outside my control, don't lose all hope yet - but also know that the formal launch date of CREST on Tranquility is not tied to being the 4th of December - we will test on a test server until we feel confident to flip the TQ switch, once the code is out with Retribution.

Is there anything concrete AT ALL as to what you are going to allow developers access beyond what is already available on the current V2 api.

so, please correct me if i got this wrong:

1. you will put CREST on TQ but leave it disabled,
2. we register for the license
3. CREST will be available to us on Testserver, we will start building our first libs against CREST
4. you monitor the impact of what we do on Testserver, and once your happy
5. CREST will be enabled on TQ
6. we can now start deploying apps to users that use CREST

Now, just a rough guess of time, and looking at the upcoming holidays, etc. this means we probably can start with the testserver in january, and it will be on TQ in February or March.
(hoping no marketing guy gets the great idea of delaying the tq release till fanfest)

is this a realistic estimate?