It has become silent in here...
Goddchen.4958:
… that might be a sign of less interest in the API or of a big thing to come some time soon (oauth2?).
What do you think? I’m personally hoping for the second option… :-)
Killer Rhino.6794:
Yeah. I think we’ve exhausted the majority of interesting things to do with the current APIs. I come back here twice daily looking for news of OAUTH enabled endpoints…that’s when things will get really going!
Drakma.1549:
I’d love to see an update from Cliff.
Maybe if we say his name three times…
Edgar Doiron.2804:
Cliff
That’s number 2
Snowreap.5174:
Cliff.
not that I am in any way superstitious.
-ken
Gudradain.3892:
Yeah. I think we’ve exhausted the majority of interesting things to do with the current APIs.
Not yet
rodadams.5963:
There’s not a lot of things left to publish that wouldn’t need oauth2.
Well, perhaps read-only info from the Trading Post. But all the other major stuff would need oauth2, I think. (Characters, Guilds, etc)
Drakma.1549:
If you’re bored… come chat!
smiley.1438:
I’m still waiting on some improvements on several API responses so that we can finally have fast and reliable wikimaps such as:
- retrieve floordata by map_id (or even better: by map name)
- sector boundaries as polylines in the floordata
- descriptions for several poi types like skill points and vistas
- correct event_type in the event_details.json
- better structure of several json responses (e.g. this, this, this, this and this)
- some more information on how to display guild emblems, since my final approach had ok results, but was far from perfect
…and many more which were already asked by others in the respective suggestion threads…
Drakma.1549:
I do hope this isn’t getting thrown to the back burner. We had a flourish of activity and then… nothing…
I’m holding out hope that I’ll come home from work on Monday and there will be 20 updates with new APIs.
LadyRhonwyn.2501:
Let’s give them some time! It’s better to think something over a second time rather than having to implement something a second time… Besides, I’m not done with my application yet :P (I keep implementing things multiple times before I’m satisfied!)
Moderator.9532:
Hello everyone, please refrain from making staff callouts in your posts. We understand that you wish for a thread to receive the attention you feel it is due, however using staff names does not aide in making this happen and is a violation of our Code of Conduct.
Drakma.1549:
I don’t think anybody meant anything bad by this. I know my post was in jest.
I think what you’re seeing is a community that is very excited about your product (both the game and the API).
Stephane Lo Presti.7258:
I think what you’re seeing is a community that is very excited about your product (both the game and the API).
We understand this, yet we don’t want to set a precedent for “call out threads” on the API Development subforum. It has been to date a great subforum and everyone has to accept that activity here can be up and down, based on API changes and generally the amount of questions API application developers have. So no reason to create activity where none is needed. We won’t take any moderation action but encourage you to not create “fillers” on this subforum, to keep its focus on actual development needs (as explained in this sticky post
Thanks for your understanding!
Goddchen.4958:
I’m really sorry for how this thread went… This is was totally not what I wanted to achieve.
Some moderator, please close this thread…
Stephane Lo Presti.7258:
I’m really sorry for how this thread went… This is was totally not what I wanted to achieve.
Some moderator, please close this thread…
Don’t be, I’m sure you only had good intentions when you created this thread. It was a good opportunity to clarify the matter and it’s allowed us to share some ground rules with everyone (so we won’t close it). Thanks for your understanding Goddchen.4958!
Lord Erik.6903:
It’s a GM! Get em! kiss his feet, and tell him your not worthy!
Stephane Lo Presti.7258:
It’s a GM! Get em! kiss his feet, and tell him your not worthy!
Oh no please!