These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Jita Park Speakers Corner

 
  • Topic is locked indefinitely.
12Next page
 

CSM7 Dec Summit Topic - CREST for 3rd parties

First post
Author
Two step
Aperture Harmonics
#1 - 2012-11-28 16:17:47 UTC
I am super excited about this

CSM 7 Secretary CSM 6 Alternate Delegate @two_step_eve on Twitter My Blog

Anna Shoul
#2 - 2012-11-28 18:19:16 UTC
Give me API that lets me programmatically pay people, and it will be possible to solve many an Eve problem well before CCP ever gets around to it. :)
Two step
Aperture Harmonics
#3 - 2012-11-28 18:34:57 UTC
Anna Shoul wrote:
Give me API that lets me programmatically pay people, and it will be possible to solve many an Eve problem well before CCP ever gets around to it. :)


I agree, and I have asked CCP to make this a priority. I suspect they want to test out a little less harmful API first, but I will be arguing for this as the very next API to make available from CREST.

CSM 7 Secretary CSM 6 Alternate Delegate @two_step_eve on Twitter My Blog

stg slate
State War Academy
Caldari State
#4 - 2012-11-28 22:49:23 UTC
Anna Shoul wrote:
Give me API that lets me programmatically pay people, and it will be possible to solve many an Eve problem well before CCP ever gets around to it. :)


This will be great, give me an API that lets me make any operation other than a READ for eve and I'll be torn between embedding it in juicy-looking malware to meta-steal from other players, or developing an eve web client so I can play from anywhere! And if that is not enough, I can fully automate anything that is non-trivial that you allow the API to do, with a robust enough API I could develop a client-less bot without all the network packet decoding getting in the way (because that stuff is a pita) !




honestly, please don't even ask them to turn on ANY sort of PUT/POST operations to update/perform anything other than simple data pulls.

I know you might feel CRESTfallen to hear this, but it is for the best!
Haryman
Aliastra
Gallente Federation
#5 - 2012-11-28 23:26:47 UTC
There are so many ways this can be abused.

Seriously, do NOT do this.
Serpentine Logic
Ministry of War
Amarr Empire
#6 - 2012-11-29 00:38:31 UTC  |  Edited by: Serpentine Logic
The absolute first thing that needs to be decided is how many write calls should be allowed per key per day.

There are a lot of calls that are really useful if available once every x hours, but open to abuse if unlimited.

For instance, it would be uber convenient to have a mobile app with a list of your open orders, and you press a button and it will -0.01 isk the competition on that order via CREST.

Once, twice, three times per day? An awesome app for traders, everyone loves it, Massively.com writes articles about it, kudos all round.

Unlimited? Bot central, Sreegs ***** bricks, everyone pans the whole idea.
EI Digin
irc.zulusquad.org
#7 - 2012-11-29 00:45:48 UTC
I too am really excited about this feature.

The thing I would be most looking forward to as an individual is being able to pull market information, be able to use my own tools and market metrics, and potentially be able to update market orders without having to load up the game. I like being able to use my own interface and tools to reduce the amount of clicks I have to make.

Another good use of CREST would be to allow corporation management. It would make third party auth systems a lot more effective as designated managers only need to push one set of buttons to change things around, not to mention allowing people to change permissions without having to log into the game.

The downside however, is that clever people will use write access ability to create efficient programs to automatically earn isk for you. And of course, the scamming metagame will shift towards obtaining full character PUSH APIs via malware or old fashioned social engineering.

Not that any of this is a bad thing in my opinion, because cleverness should be rewarded and stupidity punished, but it could clash with the rules already put in place by the GMs and the security team. Lots of people would be turned off by the idea as well, because people would be making isk for "no effort".
Serpentine Logic
Ministry of War
Amarr Empire
#8 - 2012-11-29 00:46:58 UTC
The second thing would be to work out the best apis to release first, from the point of view of demand vs risk.

Stuff with high demand and low risk are the types of things that only affect you or your corp.


  • delivering and starting industry jobs
  • sending corp evemails
  • [* adjusting contacts
  • writing to corp/alliance calendar
  • setting up corp/alliance contracts
  • resetting PI extractors
  • sending money to/from corp wallet and general corp accounting
  • delivering corp assets to members and vice versa


The next API calls involve interacting with neutrals, and should have much more stringent timers around them.

Stuff like:


  • trade orders
  • public contracts
  • public evemails
  • sending isk
etc.

so that's the order that I expect the APIs to be released in.
stg slate
State War Academy
Caldari State
#9 - 2012-11-29 18:53:00 UTC
Serpentine Logic wrote:
Stuff with high demand and low risk are the types of things that only affect you or your corp.


  • delivering and starting industry jobs
  • sending corp evemails
  • [* adjusting contacts
  • writing to corp/alliance calendar
  • setting up corp/alliance contracts
  • resetting PI extractors
  • sending money to/from corp wallet and general corp accounting
  • delivering corp assets to members and vice versa




Please expose these things, just don't tell CCP Sreegs you are going to :P


Praetor Abre-Kai
Pickling Rifles
#10 - 2012-11-29 20:54:56 UTC
Haryman wrote:
There are so many ways this can be abused.

Seriously, do NOT do this.


care to back up your baseless assertion?
stg slate
State War Academy
Caldari State
#11 - 2012-11-29 22:59:46 UTC
Praetor Abre-Kai wrote:
Haryman wrote:
There are so many ways this can be abused.

Seriously, do NOT do this.


care to back up your baseless assertion?


Serious. I. Will. Abuse. Them. (or the many people smarter than I will)

ANYTHING you expose via API will be able to be automated.
ANYTHING important that can be done via API people will develop mal-ware to do once they trick people into running it.




Two step
Aperture Harmonics
#12 - 2012-11-30 01:51:26 UTC
stg slate wrote:
Praetor Abre-Kai wrote:
Haryman wrote:
There are so many ways this can be abused.

Seriously, do NOT do this.


care to back up your baseless assertion?


Serious. I. Will. Abuse. Them. (or the many people smarter than I will)

ANYTHING you expose via API will be able to be automated.
ANYTHING important that can be done via API people will develop mal-ware to do once they trick people into running it.






Why wouldn't your malware just steal someone's EVE account details?

CSM 7 Secretary CSM 6 Alternate Delegate @two_step_eve on Twitter My Blog

JP Nakamura
Union of Intergalactic Miners and Nano Assemblers
#13 - 2012-12-05 13:45:19 UTC  |  Edited by: JP Nakamura
Two step wrote:
stg slate wrote:
Praetor Abre-Kai wrote:
Haryman wrote:
There are so many ways this can be abused.

Seriously, do NOT do this.


care to back up your baseless assertion?


Serious. I. Will. Abuse. Them. (or the many people smarter than I will)

ANYTHING you expose via API will be able to be automated.
ANYTHING important that can be done via API people will develop mal-ware to do once they trick people into running it.






Why wouldn't your malware just steal someone's EVE account details?


Not the original parent but a programmer, think about it.

For the malware to steal their EvE account details it must do something it isn't supposed to, and steal their credentials.

If you open up the APIs, then the users will GIVE their Push API keys to the program willingly for one purpose, only to have it subverted for some other purpose.

This second scenario is much more likely, is easier to program, and may/may not be noticed by the user, since they will be able to line up API access with when they use the program, and are expecting the program to use the API.

Think of it as Theft vs Embezzling.

Also, as mentioned above, anything that can be done via the API *WILL* be automated, once that's done, people will flock to download those programs and give them their API keys (which have traditionally been safe and Read Only), which will introduce a natural an unprotected attack vector.

CCP: 10+ years of Harvesting players Tears  (latest efforts being Source Limited Edition, and Alliance Logo Revised Policies)

Two step
Aperture Harmonics
#14 - 2012-12-05 13:56:38 UTC
JP Nakamura wrote:


Not the original parent but a programmer, think about it.

For the malware to steal their EvE account details it must do something it isn't supposed to, and steal their credentials.

If you open up the APIs, then the users will GIVE their Push API keys to the program willingly for one purpose, only to have it subverted for some other purpose.

This second scenario is much more likely, is easier to program, and may/may not be noticed by the user, since they will be able to line up API access with when they use the program, and are expecting the program to use the API.

Think of it as Theft vs Embezzling.

Also, as mentioned above, anything that can be done via the API *WILL* be automated, once that's done, people will flock to download those programs and give them their API keys (which have traditionally been safe and Read Only), which will introduce a natural an unprotected attack vector.


CCP Seagull has mentioned in the past that in order to build a CREST app people would have to register with CCP. This would mean that anyone building such an app would be found by CCP. I would also imagine that the number of people that would be giving some random app the ability to send ISK would be very low.

In this case the benefits *far* outweigh the risks. There are a lot of people that could greatly simplify their lives with the ability to automate ISK payments. For example, wormhole corps like mine gather up sleeper loot, sell it and then have to split the ISK. Nullsec alliances need to reimburse people for ship losses. Hell, the current bounty system could have been implemented entirely with CREST.

CSM 7 Secretary CSM 6 Alternate Delegate @two_step_eve on Twitter My Blog

Anna Shoul
#15 - 2012-12-05 16:18:41 UTC
Two step wrote:
Hell, the current bounty system could have been implemented entirely with CREST.


That was my very first thought when I heard that we might get CREST, "I can implement most of Malcanis' bounty proposal without waiting for CCP to do that!" Everything except the kill rights could be done with CREST. As long as there's someone popular who will lend their name to it, it would be trivial to hand them the source code and let them run it. :)

But let me make a list of other things that can be possible if the only thing CREST allows you is paying people:

  1. You can run a corporation like it's a corporation and not a commune. You can automatically and impartially pay people for the performance of specific duties -- as long as the performance of these duties can be programmatically detected, the code can pay for them. Mine for the corp, get paid for what you drop into the corp hangar. Kill the corp's enemies, get paid per head - or per ship class or whatever. Trade for the corp, get a share of the profit from the orders you have managed. The relationship can be arbitrarily complex, from weekly salary and automated performance review, to immediate reaction as soon as the performance of a duty is registered anywhere.
  2. You can set up an automatic ship reimbursement program.
  3. The potential for IGB-based derivative trading services is pretty much immeasurable. And while there's a lot to be said about derivatives, much of it not very nice, the Eve economy would move that much faster.
  4. You can have an automatic escrow service capable of determining if the breach of contract has occurred. The most obvious use of which would be a programmatically enforced pirate ransom contract. Proper by-the-book piracy could become a reasonable business once again.


I could probably go on, that's just what I can think of in ten minutes.
stg slate
State War Academy
Caldari State
#16 - 2012-12-06 15:10:59 UTC
You can say what you want, I am not going to argue to convince you NOT to open a security hole that I'm personally very excited to be in game.

I'm just informing you guys so you cannot claim ignorance when it blows up in your face.
Dei
Cosmic Core Industries
#17 - 2012-12-10 17:45:15 UTC  |  Edited by: Dei
Well, apart from the pure speculation that everyone in this thread is doing, we need specific details on what CCP are actually planning.

What we need to know is:


  1. How many developers are working on CREST
  2. Is the EVE API staying as Read-only or will it be superseded by CREST
  3. How much overlap does CREST take on the current API
  4. What operations will be available?
  5. What are the costs for 3rd party devs?
  6. How do we get compensated for making CCP's product better?
  7. Are CCP planning to take over market metrics such as Eve Central with real market access?
  8. Where does static data dump fit into all of this?
  9. Is anyone planning to standardise the static data dump?
  10. Does CCP realise how much 3rd party developers need metadata access before patch releases?
  11. What are the limits to calls (if any), and what is their stance on automated market arbitrage?
Nik W
Critical Mass Inc.
#18 - 2012-12-10 17:48:01 UTC
What could possibly go wrong?

This is a bad idea, looking for bad people to make it do bad things.

Can we finish the read only API first at least? I got here from a link in another thread talking about how CCP can't even put out an accurate data dump within a week of a release. There is no way this is going to be done correctly. Not. A. Chance. In. Hell.

Also, last time I checked, CCP wanted people to play the game.

This idea needs to be nuked, and never spoken of again.
Two step
Aperture Harmonics
#19 - 2012-12-10 17:49:08 UTC
Dei wrote:
Well, apart from the pure speculation that everyone in this thread is doing, we need specific details on what CCP are actually planning.

What we need to know is:


  1. How many developers are working on CREST
  2. Is the EVE API staying as Read-only or will it be superseded by CREST
  3. How much overlap does CREST take on the current API
  4. What operations will be available?
  5. What are the costs for 3rd party devs?
  6. How do we get compensated for making CCP's product better?
  7. Are CCP planning to take over market metrics such as Eve Central with real market access?
  8. Where does static data dump fit into all of this?
  9. Is anyone planning to standardise the static data dump?
  10. Does CCP realise how much 3rd party developers need metadata access before patch releases?


Why do you need to know how many devs are working on CREST?

The current API will always be read only, CREST is the writable API system.

Costs have already been discussed, they will be $0.

CCP isn't going to pay you for 3rd party apps, if that is what you are asking. Details on allowing ads and whatnot are forthcoming.

The SDD is a big issue, and I will certainly be bringing it up.

CSM 7 Secretary CSM 6 Alternate Delegate @two_step_eve on Twitter My Blog

Dei
Cosmic Core Industries
#20 - 2012-12-10 18:04:17 UTC
Two step wrote:

Why do you need to know how many devs are working on CREST?


Because progress is slow. I guess I'd like to know what the hold up has been considering there has been extremely little communication about it and a lot of promises.

Two step wrote:

The current API will always be read only, CREST is the writable API system.


Then is the current API going to be put in maintenence mode? What kind of developer resourcing are they dedicating to both APIs compared to pre-CREST?

Two step wrote:

Costs have already been discussed, they will be $0.


0 licensing? Anyone can register an app? Any registration processes or approval process?

Two step wrote:

CCP isn't going to pay you for 3rd party apps, if that is what you are asking. Details on allowing ads and whatnot are forthcoming.


Not directly, I meant more the ethics on charging customers a percentage on 3rd party developer calls. For instance banking - the bank siphons off 1% per transaction into the developers account. Is it a free for all for this kind of thing?

Thanks for the reply. :)
12Next page