|
Author |
Thread Statistics | Show CCP posts - 2 post(s) |
Catari Taga
Centre Of Attention Middle of Nowhere
|
Posted - 2010.07.19 19:00:00 -
[1]
Edited by: Catari Taga on 19/07/2010 19:00:52 Thanks for the log.
tl;dr: it's not Atropos' area of responsibility to know why EVEGate features are not available as an API, and because of their SCRUM approach they cannot have a dedicated API dev.
In other words, same old. --
Originally by: CCP the data does not seem to support that polished quality sells better than new features
|
Catari Taga
Centre Of Attention Middle of Nowhere
|
Posted - 2010.07.19 22:11:00 -
[2]
It wouldn't really need any direct communication even, it should be plain enough what 3rd party developers need, and pre-EVE Gate there had been forum communication between devs and developers about our request of making the system open and their refusal. So I don't really think there's any communication issue but rather a deliberate choice which has been made. --
Originally by: CCP the data does not seem to support that polished quality sells better than new features
|
Catari Taga
Centre Of Attention Middle of Nowhere
|
Posted - 2010.07.21 14:00:00 -
[3]
Originally by: azo jigga but im not certain if CSM is the place for this interface.
--
Originally by: CCP the data does not seem to support that polished quality sells better than new features
|
Catari Taga
Centre Of Attention Middle of Nowhere
|
Posted - 2010.07.22 08:11:00 -
[4]
Edited by: Catari Taga on 22/07/2010 08:15:37
Originally by: Hel O'Ween
Originally by: Verite Rendition [...] some of this is just us asking for too much (i.e. write access).
People really have asked for write access via API? I didn't hear that before.
Even non-techies agree in the API being read-only is a very good thing (just if there could be more of it ), because most people do realize that API write access = macroers heaven.
The write access discussion was in conjunction with EVEGate. EVEGate allows write access to TQ for mail, contacts and calendar. The API does not even allow full read access for mail and no write access to any of those. So what people, myself included, are doing, is to write tools that provide write access via EVEGate instead of a defined API, also requiring you to enter your account's login details rather than an API key, which of course is against the EULA if shared. The reason is not only ease of use/integration but also the bad quality of EVEGate which is incompatible with many browsers, in particular on mobile devices (and at least for the people I know remote access to evemail is mostly done while traveling, using mobile devices).
There is nothing remotely relevant to macroing in asking for access to EVEGate functionality via a defined API. We will access it either way.
Originally by: Hel O'Ween But having a 3rd party dev amongst the CSM would do wonders for simple fixes.
You may have been missing the recent CSM minutes plus dev blog and ensuing threadnaughts. The reality is the CSM is entirely powerless and cannot do anything more than a simple forum post could do, too. In addition, the low frequency of CSM-CCP interaction makes a forum post (or other means of communication) many times more effective than the CSM. The CSM may still have its uses but it cannot achieve what you hope from it. --
Originally by: CCP the data does not seem to support that polished quality sells better than new features
|
Catari Taga
Centre Of Attention Middle of Nowhere
|
Posted - 2010.07.23 12:42:00 -
[5]
Originally by: Hel O'Ween
Originally by: Catari Taga
Originally by: Hel O'Ween But having a 3rd party dev amongst the CSM would do wonders for simple fixes.
You may have been missing the recent CSM minutes plus dev blog and ensuing threadnaughts. The reality is the CSM is entirely powerless and cannot do anything more than a simple forum post could do, too. In addition, the low frequency of CSM-CCP interaction makes a forum post (or other means of communication) many times more effective than the CSM. The CSM may still have its uses but it cannot achieve what you hope from it.
But than again the CSM meeting minutes stimulated that dev blog, which in turn stimulated a threadnaught = it gets attention, while the dirty dozen 3rd party devs just ramble in the Tech Lab Forum and get mostly ignored both by the players (which is OK) and CCP. At least it feels that way.
True that, although you could question whether neglected 3rd party dev requests would lead to the same kind of reaction. In any case I'll agree that having a 3rd party dev in CSM will be a bonus.
Also I think the number of 3rd party devs is quite a bit higher than those who post here or are on IRC.
Originally by: Tonto Auri
Originally by: Hera Vertigo Edited by: Hera Vertigo on 23/07/2010 06:20:08 The dev team has just gotten to big. And frankly I don't think they really care because the API does not convert into $$$ for CCP. And when you get too big it all comes down to $$$.
Not true in the $$$ sentence. API is probably the best advertising instrument in their posession.
I agree with that, datadump, image dump and API, or rather the websites and tools that spring from it, are a big part of the attraction of the game for many people. --
Originally by: CCP the data does not seem to support that polished quality sells better than new features
|
|
|
|