EDDN does not block publisher or subscriber in that, you will have to ask both of them.
Sorry, don't understand your answer.
What I say is that as far as EDDN is concerned, we do not block publisher (EDMC in your case) to send informations to subscriber (EDDB in your case).
So we cannot say why your commodities prices were not pushed to EDDB or any other trading site using EDDN to gather informations.
Ah OK, then I think you misunderstood my question. EDMC is getting a message back from FD Companion API that there is no commodity market, but in fact there is. In that case, are there other ways that I can get the data to EDDB (other than OCR)?
Manuell input?
eg. Tradedangerous has an manuell input mode where you can edit the market of an station, maybe EDDB does have something like this if you're registered (it's called ROSS).
Yep I'm using the TD feature to update my local copy of TD data, and upload it to maddavo too, but as I understand it maddavvo cannot send the data to EDDB.
EDMC, EDAPI (for use with TradeDangerous) and EDCE use Frontier's API.Please can somebody tell what community tools can send data to EDDN. I know about EDMC, but what else can do this please?
Hey guys,
As promised we've discussed the topic for you all, sorry for the delay in replys but today was the first available opportunity to review the thread.
People are free to continue use of the existing companion app API, though please be aware this is something we hope to expand and improve on the future. Since we don’t yet have a date for that, use of the existing one is fine, but we ask that you do so in a careful and considered manner – for example not polling it continuously. We will bring in guidelines and an approval process over time too, but for now please be aware that we will stop apps that are not well behaved.
We are passionate about the development of community created content and very much see the value in the tools that are being created which is why we are happy for this API to be continued. As we have mentioned before, we would like to create a new API which allows tool developers support to create their own tools but this will not be a short term implementation and is instead something we are considering for future development.
Thanks for your patience, we will keep you informed as and when we have more information to share.
EDMC, EDAPI (for use with TradeDangerous) and EDCE use Frontier's API.
EliteOCR and Regulated Noise use OCR.
Thanks. I wasn't clear enough with my question. What I meant to say was...
"Are there any tools where you input prices manually, and those prices are then sent to EDDN?"
<snip>
Might I ask why you are looking for such a tool?
Thank you for the comprehensive reply.
I have an unusual 'use case'. I'm part of a fan faction that Frontier have created in the game 8th Dragon Squadron. The very first place we expanded, EDMC cannot send the data to EDDN because the API says there is no market, but there is.
EliteOCR does not work anymore, RegulatedNoise crashes every time I try to use it.
So I'm looking for another way to get data for this particular station (and others, there are many) into EDDN.
FYI, I have uploaded the prices to maddavo, it's clear his site has not passed them through to EDDN, as EDDB.IO is not showing the update.
Afaik EDCE is pretty small. It can also be used as a library. This might be something to look at for a start. Will give it some more thought tomorrow. Are you a coder or are their coders in your group?
So I'm capable of writing PHP and could make a version of this link work for me.
My thinking is that I would use the Trade Dangerous editor to manually key the prices if EDMC cannot send them. TradeDangerous produces an updated.prices file. I can write PHP that would parse the .prices file and send to EDDN.
My worry though is whether the EDDN subscribers would accept my 'application' from the EDDN or just chuck it away.
I'd have to learn Python to integrate this into TradeDangerous....
But if there's something out there I can use instead, that would be my preference.
Hi DRY411S,
There should be no problem for your application to send the data.
I am not aware of application being refuse, but it could be, we tend to love the API data because they help us clean the things.
[TABLE="class: highlight tab-size js-file-line-container"]
[TR]
[TD="class: blob-code blob-code-inner js-file-line"]// A sample list of authorised softwares
$authorisedSoftwares = array(
"EDCE",
"ED-TD.SPACE",
"EliteOCR",
"Maddavo's Market Share",
"RegulatedNoise",
"RegulatedNoise__DJ"
);
// Used this to excludes yourself for example has you don't want to handle your own messages ^^
$excludedSoftwares = array(
'My Awesome Market Uploader'
);[/TD]
[/TR]
[/TABLE]
Your best bet is a trading tool where users can upload their data which is then distributed to EDDN. BUT you have NOT found one it seems.
My concern comes around the EDDN github sample code where there are examples for subscribers to reject EDDN messages unless the application is in a list. Example:
Code:[TABLE="class: highlight tab-size js-file-line-container"] [TR] [TD="class: blob-code blob-code-inner js-file-line"]// A sample list of authorised softwares $authorisedSoftwares = array( "EDCE", "ED-TD.SPACE", "EliteOCR", "Maddavo's Market Share", "RegulatedNoise", "RegulatedNoise__DJ" ); // Used this to excludes yourself for example has you don't want to handle your own messages ^^ $excludedSoftwares = array( 'My Awesome Market Uploader' );[/TD] [/TR] [/TABLE]
If subscribers have implemented code like that, which only accepts messages from authorised software then I may be wasting my time, or will have to contact each subscriber individually and ask them to include me as 'authorised'. And because my solution relies on manual input of data, I'd understand why they may say no.
Actually I HAVE. ED-TD.SPACE will allow authorised people to update data, and the EDDN github wiki claims that they are publishers. So far no luck contacting ED-TD.SPACE, and then again the Wiki also claims that Maddavo publishes to EDDN, and I'm pretty sure that isn't true.
In the meantime, I'll keep manually updating, and uploading to maddavo so at least the TD community can have this data.
That is just a complete example of what can be done, it was added when some version of EliteOCR where bugging, but I'm not sure it is used.
I am sorry for ED-TD, I have not responded to you! Well you weren't there when I came back
At first I was authorizing manual update, but I removed it in favor of 100% EDDN, the form was really hard to maintain and to submit,
one day they were more commodities than PHP could handle in his post request so I simply removed it.
One thing we could think of, is to re enable that form but doing the JSON conversion on client side to send to EDDN.
And yes, the Wiki and readme about EDDN is not actualised. I will do it when I got some time.