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

[seeebek]

Given that a bit of work has to be done updating other things due to the Powerplay release, and I would actually like to have some time to play and then there is stuff IRL, I'm not in favour of transitioning in such a short timeframe. Plus I have enough self-imposed pressure, I don't need more pressure from angry users and don't see it as a positive.

Can you push that back a week please?

I decided to implement v2 this weekend and support it for one week parallel to v1. I will use two buttons each for one version so testing would be possible.
I made the decision because themroc the author of eddb.io is travellling this week and will not be able to switch during that time.

 

[Snake Man]

Please don't do that, just wait a week once EDDB is upgraded and Maddavo's Market Share is on board too.

 

[jamesremuscat]

PSA: EDDN will have a short downtime overnight tonight (probably near 11pm UTC) to deploy v0.4.

This brings AnthorNet's many contributions into the main build.

For clarity: both v1 and v2 of the schemas will be supported in this release. We encourage software developers to move to v2 of the schema, as support for v1 will be dropped at the gateway level eventually. We have no timeframe for when this will happen, but notice will be given here.


Until then it's up to developers to decide if they maintain parallel support for v1 and v2, or just v2. Anyone writing new code (welcome!) should start with v2.

 

[AnthorNet]

For your information, we have a set of examples here: https://github.com/jamesremuscat/EDDN/tree/master/examples

You might find in the complete examples some conversions between v1 and v2 that might help you switching.
The best is to convert v1 messages to v2, so you can easily have both running seamlessly.

We have added in the github readme a list of tools using EDDN and there current status, feel free to PM to be added.

 

[Eggplant!]

Quick dumb question... please direct me to a better place to ask if needed.

Does it matter which gateway you use to send messages? Do the gateways talk to each other? I've noticed when adding eddn support (v2 only, not bothering with v1) That messages sent to a gateway are only heard on the associated relay.

If this is expected, what's the point of having two partitioned networks?

 

[jamesremuscat]

Update: There was a problem with the deployment and I've rolled back to v0.2.1 until it's not the middle of the night and I can resolve it. (The status/monitor page is not coupled to that version, though, so that has been updated.) Service has been resumed.

- - - Updated - - -

Quick dumb question... please direct me to a better place to ask if needed.

Does it matter which gateway you use to send messages? Do the gateways talk to each other? I've noticed when adding eddn support (v2 only, not bothering with v1) That messages sent to a gateway are only heard on the associated relay.

If this is expected, what's the point of having two partitioned networks?

Not a dumb question at all. The v0.4 deployment (see above) will add AnthorNet's new gateway and relay into the network, but until that happens they're not connected.

I think Anthor's plan is that consumers will be able to connect to specific relays for specific types of data, but publishers will be able to upload to the gateway of their choice. For now, until the additional data starts to exist, the 'safe' option is to use eddn-gateway.elite-markets.net, the original gateway, and subscribe to eddn-relay.elite-markets.net.

I hope that's coherent - it's half midnight here and I'm very tired!

 

[AnthorNet]

Quick dumb question... please direct me to a better place to ask if needed.

Does it matter which gateway you use to send messages? Do the gateways talk to each other? I've noticed when adding eddn support (v2 only, not bothering with v1) That messages sent to a gateway are only heard on the associated relay.

If this is expected, what's the point of having two partitioned networks?

There is not quick dumb questions ! Effectively I haven't talk about that new gateway/relay, but it appears on the status page.
As for now (before 0.4 appears on the main relay version), only eddn-relay.ed-td.space is connected to both gateways.

The goal is that all relays are connected to all gateways, then we can have some relays passing more information, without losing anything or boring anyone else.

I'll add some documentations about all that when I have little time. I think after the transition to v2 is well done.

EDIT: Never mind I suppose. It's working now. It's just somewhat inconsistent whether or not my receiver sees the post.

Now I understand why your were receiving half of the message, the o.4 release adds a deduplicate function, thus a same message don't pass a second time within a 15 minutes window.
I remove the deduplicate from test message yesterday to make it easier to test.

 

[maddavo]

Progress: I think I've got a v1/v2 listener/parser all working OK now.
For sending, I'll dual-send v1/v2 for a week.

@AnthorNet, that status page is sooo useful - tks! Who is "EOda554f6d"??? haha.

 

[AnthorNet]

Progress: I think I've got a v1/v2 listener/parser all working OK now.
For sending, I'll dual-send v1/v2 for a week.

@AnthorNet, that status page is sooo useful - tks! Who is "EOda554f6d"??? haha.

Some software are sending hashed name

 

[Eggplant!]

Thanks jamesremuscat and AnthorNet!

I think part of my confusion was in following the github example. It randomly posts to one of the two gateways, so I did the same thing in my code thinking that was the way to go. I guess it's not quite ready for that just yet.

- - - Updated - - -

Some software are sending hashed name

Speaking of this... what is acceptable here? I saw some some software uses a commander name, and some obfuscates that with a hash. I went with the hash thinking that some folks might be upset about broadcasting their commander name, but you can still track bad apples with a hash.

 

[Eggplant!]

Progress: I think I've got a v1/v2 listener/parser all working OK now.
For sending, I'll dual-send v1/v2 for a week.

@AnthorNet, that status page is sooo useful - tks! Who is "EOda554f6d"??? haha.

Nice job! I just tested posting EDDN v2 from my app and it showed up in maddavo's! Hooray!

 

[jamesremuscat]

OK, taking the network down briefly to try deployment of 0.4 again.

Update: v0.4 has been successfully deployed. Happy data sharing

 

[Snake Man]

And so the chaos begins

 

[AnthorNet]

And so the chaos begins

You know 0.4 does not have anything to do with v2 commodity....
It's about internal changes and deduplicate

 

[AnthorNet]

With the appearing of new software and lot of new versions, the software status table was a mess!
It is now corrected, the table only show software with all versions, to see detail of specific version of software, you just have to click on it.

See: http://eddn.ed-td.space/

Hope you'll find that useful and easier to read.

It might be some polish, but it works.

 

[jamesremuscat]

And so the chaos begins

Could you explain?

 

[Otis B.]

With the appearing of new software and lot of new versions, the software status table was a mess!
It is now corrected, the table only show software with all versions, to see detail of specific version of software, you just have to click on it.

Very nice.
However clicking on an entry opens a box containing an empty table for me on FF or Safari. i.e just

Maddavo's Market Share	Today hits	Yesterday hits	Total hits

but no content.

 

[AnthorNet]

Very nice.
However clicking on an entry opens a box containing an empty table for me on FF or Safari. i.e just

Maddavo's Market Share	Today hits	Yesterday hits	Total hits

but no content.

Fixed ! Thx. Chrome did not whine about that error !

 

[AnthorNet]

Speaking of this... what is acceptable here? I saw some some software uses a commander name, and some obfuscates that with a hash. I went with the hash thinking that some folks might be upset about broadcasting their commander name, but you can still track bad apples with a hash.

It depends, the best is to ask for your user, with a checkbox for example, if they want to send data anonymously or with their CMDR name.

 

[wolverine2710]

With the appearing of new software and lot of new versions, the software status table was a mess!
It is now corrected, the table only show software with all versions, to see detail of specific version of software, you just have to click on it.

See: http://eddn.ed-td.space/

Hope you'll find that useful and easier to read.

It might be some polish, but it works.

Its beautiful. Missed this post but saw the new version. At first I thought, less detailed but then I found out that clicking on a publisher shows the details. Very very nice.

On a sidenote. It looks as if EDMC as of yesterday is sending more data to the EDDN then good old EliteOCR. Today at this moment EDMC has send more then twice the amount of data then EOCR. Sooo, its taking off. As mobile api based tools are "OCR eror free" as mentioned by Seebek it means a lot of pristine data. Its however a pity that most data of EDMC is sent in V1 not V2 and cmdrs haven't upgraded all to the newest version. 1.3.4 is schema V1. EDMC 1.4.0+ is schema V2. EDCE and EDAPI are also sending data ;-) When comparing V1 and V2 data please remember that V2 sends one msg with all prices in one go instead of each message having one price inside. Hence multiply V2 with say 50 times to compare it with V2. For urls for EDAPI, EDMC and EDCE see the OP.