Release EDDN - Elite Dangerous Data Network. Trading tools sharing info in an unified way.

Status
Thread Closed: Not open for further replies.

wolverine2710

Tutorial & Guide Writer
Oh blast, no wonder nobody has been PMing me :eek:

I've received no requests as yet (though the above might have something to do with that!) and yes Christmas tree is ongoing - maybe an alpha soon.

Edit: Enabled PMs. Let me know if still can't do so.


Could succesfully send you a PM. Emails seems to be activated as well,didn´t test it though.
Ho ho ho a late Xmas gift,nice ;-)
 
I don't know to whom it concerns, but I'm seeing a lot of very slow traffic on EDDN of the form:

{'dynamoTimestamp': 1422135848550663L, 'json': '{"header": {"softwareVersion": "v0.2.3", "gatewayTimestamp": "2015-01-24T21:44:08.592974", "softwareName": "ED Central Production Server", "uploaderID": "54c3e1ea34593ad2e53a66b0"}, "$schemaRef": "http://schemas.elite-markets.net/eddn/commodity/1", "message": {"buyPrice": 0, "timestamp": "2015-01-24T19:36:06+00:00", "stationStock": 0, "systemName": "39 Tauri", "stationName": "Porta", "demand": 23453, "demandLevel": "Med", "itemName": "Coffee", "sellPrice": 1598}}', 'gatewayEpochMicro': 1422135848592974, 'gatewayDay': '2015-01-24', 'gatewayEpochMilli': 1422135848592}

I'm pointing it out because ED Central Production Server has been updating 39 Tauri, Porta Station (& occasionally 39 Tarui, Porta Station) for at least an hour, with a very slow dripfeed of messages - in some cases, a single update stretches over 20 minutes for the same station without a break.
 
Last edited:
I don't know to whom it concerns, but I'm seeing a lot of very slow traffic on EDDN of the form:



I'm pointing it out because ED Central Production Server has been updating 39 Tauri, Porta Station (& occasionally 39 Tarui, Porta Station) for at least an hour, with a very slow dripfeed of messages - in some cases, a single update stretches over 20 minutes for the same station without a break.

Indeed! I sent a message to CMDRKNac who assumable runs ED Central. Let's hope he will fix his service :)
 
A very early pre-alpha build of a real time feed for EDDN can currently be found at http://167.88.112.220/. I should emphasise the following:

  • Purely a dev server - it's not set up for load as yet - please preview rather than widely advertising.
  • Very very early proof of concept - in the spirit of Agile, getting it out there to potential consumers for a first look while I work on remaining features
  • The real version will have a DNS, proper API pages, etc. - when happy with it, probably move it to Github too
  • I reserve the right to take down said dev server at a moment's notice ;) The real one I'll probably run load-balanced, but still pondering best infrastructure.
  • This is purely EDDN's JSON that matches the schema. No cleaning up is occurring as yet.
  • It's hard-limited to last 10 results currently - I intend to make this more flexible later.
  • I'm only testing in Firefox at present - like any good developer I'll test in Chrome & IE, but right now, just getting stuff working at all.

The 3D stuff isn't turned on yet - I have something working, but not really happy with the results yet. Needs more iterations.

Bug reports & feedback welcome via PM.
 
Last edited:
Do you guys think that there would be any interest in adding the ability to report pirate activity to the trading tools? If it's possible and there's the interest from the traders and trading tool developers, I'd be interested in developing a tool to to allow interested parties to access those reports.
 
There was a massive amount of messages that came through for "Esuseku/Savinykh Orbital" from both RegulatedNoise and EliteOCR. I am not sure if someone is messing with the feed or not.

EDIT: Ah, just noticed the "test" schema being used. Never mind. :D
 
RegulatedNoise is by default using "test" schema, there is tickbox to remove it and 99% of the average users out there will not ever do that :(
 
And yet there are others testing without the test schema :(

Code:
{"softwareVersion":"0.4.1.3","gatewayTimestamp":"2015-01-27T06:08:43.162048","softwareName":"BPC2EDDN","uploaderID":"EOb4b99478"}
{"header": {"softwareVersion": "0.1.0.0", "gatewayTimestamp": "2015-01-27T06:10:00.606065", "softwareName": "BPC2EDDN", "uploaderID": "allBPCusers"}, "$schemaRef": "http://schemas.elite-markets.net/eddn/commodity/1", "message": {"buyPrice": 0, "timestamp": "2015-01-27T06:05:00+00:00", "stationStock": 0, "systemName": "Frigaha", "stationName": "Onizuka Landing", "demand": 999999, "sellPrice": 2359, "itemName": "Reactive Armour"}}
 
I think I'm going to have to add in a gateway-based blacklist for this. It's pretty poor from whoever's behind BPC2EDDN, but at least I know the two IP addresses it's using...

Ideally there would be a method of upvoting or downvoting feeds/entries/softwares/IPs, à la Reddit. It would avoid you having to manually filter out stuff. :)
 
Ah.. that explains it.
I looked on my status screen today (which shows no. of system uploads in the last hour) and it was in the hundreds! It's at least 8-10 times the norm.
I rather just assumed that Slopey was now uploading to EDDN, but no, it's this "BPC2EDDN".
I must admit I'm pretty peed off - I explicitly *didn't* have the TEST stream going to my data - and that's exactly what this looks like, test stuff. Not impressed.
I'm just going to have to filter out "BPC2EDDN" for now.

Chris.
 
Ah.. that explains it.
I looked on my status screen today (which shows no. of system uploads in the last hour) and it was in the hundreds! It's at least 8-10 times the norm.
I rather just assumed that Slopey was now uploading to EDDN, but no, it's this "BPC2EDDN".
I must admit I'm pretty peed off - I explicitly *didn't* have the TEST stream going to my data - and that's exactly what this looks like, test stuff. Not impressed.
I'm just going to have to filter out "BPC2EDDN" for now.

Chris.

anyone told the author about that screwup?
 
anyone told the author about that screwup?

I went to Slopey's thread and asked (nicely), and it wasn't him. So we don't know.

ancient-aliens.jpg
 
I guess we need to talk about whitelisting and what sources are actually useful. The data coming from that source could be how old? months? Doh :( And it's on eddb already. Still not sure if a rollback is worth it :(
 
I guess we need to talk about whitelisting and what sources are actually useful. The data coming from that source could be how old? months? Doh :( And it's on eddb already. Still not sure if a rollback is worth it :(

Well, we kinda avoided that question to get things rolling, but it is becoming inevitable. So it's whitelisting vs blacklisting, and in both cases it requires management.

If it is a whitelist, some kind of api key generator needs to be made associated with a developer's email address, which requires signature/verification capability. It can't just be IP based, since the clients can be anywhere.

EDIT: it could just be assigning a secret to the developer to his email address, and have the client hash the message with it, James verifies the hash and lets it through if it matches. Not super duper secure, but should be annoying enough to discourage most.
 
Last edited:
Well I think we can not avoid vanalism. Somebody could just clone any key. Our best bet would be to have a wiki somewhere with "known" feed signatures, so whitelisting can be done easily.
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom