The Deep Space Support Array (DSSA) | A FleetComm Initiative

[Erimus Kamzel]

Just dropped into DSSA Distant Worlds, had a quick drink with the barkeep and gave your crew some work to do, 7,280t of Tritium delivered.

That's awesome

Its been a while since someone delivered Tritium all the way out to Beagle Point, but your delivery has now provided enough to fully refuel one of the DW3 fleet carriers for its journey home (should there be a DW3).

Very much appreciated Olley

 

[Darkfyre99]

I'd just like to give my thanks to the NECFC Muninn for the R&R!

Spoiler: NECFC Muninn

 

[Lowbee]

Interesting (and sad) side note, the EDMC Passport System 1.3 plugin seems to have stopped working after updating EDMC for Odyssey.

 

[K Olley]

DSSA Distant Worlds now fully topped up, If there is a DW3 give us a shout, always willing to lend a hand.

 

[Deleted member 240115]

Interesting (and sad) side note, the EDMC Passport System 1.3 plugin seems to have stopped working after updating EDMC for Odyssey.

There's several things that EDMC 5 does a little differently that break some plugins. I'd suggest, if EDMC passport has a github page, checking the issues section and seeing if it's been brought up to the plugin devs.

I've been super busy lately updating ATEL-EDMC for EDMC to play nice with Odyssey "juicer" scan info.
Might just have to give the folks who do EDMC passport a little time to update it.

 

[Lowbee]

There's several things that EDMC 5 does a little differently that break some plugins. I'd suggest, if EDMC passport has a github page, checking the issues section and seeing if it's been brought up to the plugin devs.

I've been super busy lately updating ATEL-EDMC for EDMC to play nice with Odyssey "juicer" scan info.
Might just have to give the folks who do EDMC passport a little time to update it.

seems to be logging carrier dockings again after the latest EDMC update, but still won't add landings from older log entries. i hope it all gets worked out. i'm just glad folks make these plugins for us to use.

 

[Deleted member 240115]

seems to be logging carrier dockings again after the latest EDMC update, but still won't add landings from older log entries. i hope it all gets worked out. i'm just glad folks make these plugins for us to use.

I'm not aware of any EDMC plugins that send data "after the fact". They might..... I'm just not aware of them.

EDDiscovery will send unsynced events.

 

[Lowbee]

I'm not aware of any EDMC plugins that send data "after the fact". They might..... I'm just not aware of them.

EDDiscovery will send unsynced events.

oh, i was talking about the plugin's option to load landings from reading cmdr logs on my drive and sending them to DSSA.

 

[Cometborne]

seems to be logging carrier dockings again after the latest EDMC update, but still won't add landings from older log entries. i hope it all gets worked out. i'm just glad folks make these plugins for us to use.

These might be some of the carriers that are not supported by EDPS. THe EDPS plug-in has its own hardcoded list of DSSA carriers, and that list has not been updated since EDPS 1.3 was released in September 2020. As a result, EDPS only reports 82 DSSA carriers, while the official DSSA tracker at bit.ly/dssanetwork reports 92 operational carriers. On top of that, I know from personal experience that there are at least two carriers that changed either their name or their callsign since Septermber 2020, so there are at least 12 carriers that will not register. There might be more, I really need to find the motivation to extend my DSSA bot to also download the plugin source, and finally add the comparison functionality between the various tracker sheets that exist. One of these days, maybe.

The source code for the EDPS plugin is on github, and it would be relatively easy to fork that, update the carrier list of the plugin, and release a new version. The biggest challenges would be to get the word out that there is a new plugin version from a new maintainer, and getting people to trust that new maintainer.

However, there is also the edps.dev website, which also has a database of the DSSA carriers it supports. The source code for that website is not public, which makes it impossible to frok and update it. And running a plugin with an updated FC list against a website that has not been updated would most likely result in a mess, and that is why I have not forked the plugin.

There has been no message from the EDPS developer on the EDCD discord channel for EDPS since October 2020, and no messages on the EDPS discord since January 2021.

With the one year anniversary of the DSSA coming up and probably various carriers changing because their planned one year deployment is over, things are probably going to get worse over the next weeks and months.

Sorry to be the bearer of bad news.

 

[Deleted member 240115]

With the one year anniversary of the DSSA coming up and probably various carriers changing because their planned one year deployment is over, things are probably going to get worse over the next weeks and months.

One year or two? I know to get the GMP entry you had to demonstrate a minimum of two years upkeep.

 

[Orvidius]

Ooof, that does sound like a mess. It probably would be best to fork the project or start something entirely parallel. I think technically the tracker spreadsheet here is considered to be the most authoritative source of DSSA carrier info, so the plugin probably should have tried to use the sheet for its list of carriers. That's how I still populate the DSSA carriers for the EDAstro galmap too.

 

[Cmdr Lord melchitt]

Coming up to my second year in Errant Marches with may carrier, applied to DSSA at the start and will be spending another year out there doing my thang. Still happy to hop onboard if help needed.

 

[Cometborne]

One year or two? I know to get the GMP entry you had to demonstrate a minimum of two years upkeep.

The first post in this thread states that minimum commitment for the DSSA is one year:

Once deployed, your carrier must remain in the original system indicted in the DSSA Tracker through the 'Operational Until' date you have selected (which must be at least one year).

The second post in this thread states that to earn a permanent GMP entry, you need to be on station for at least two years.

• Your POI is considered temporary and will only remain on the maps for however long your Carrier is part of the DSSA (with permanent status being earned as outlined below).
• If you complete 2 years continuous DSSA service in a fixed location, your POI will become permanent - even if you decide to leave the initiative and move on after those 2 years. Your permanent POI will be registered as a historical location or colony (depending on how the DSSA evolves over time), and it will be a testament and acknowledgement of your DSSA service for ever more.

Neither of them talks about "demonstrating two years upkeep".

 

[Deleted member 240115]

The first post in this thread states that minimum commitment for the DSSA is one year:

The second post in this thread states that to earn a permanent GMP entry, you need to be on station for at least two years.

Neither of them talks about "demonstrating two years upkeep".

I thought it was two years for everything. Thanks for the clarification.

I remember shortly after deployment being asked to make sure my FC's had two years upkeep. Have to go find that post.
Probably somewhere in the GMP thread. Can't remember off hand.

 

[Rudi Raumkraut]

FDev decided to go on lying their customers straight into their faces and
still defending their released piece of sh i t which won't get any better,
so a second year of upkeep will not be necessary

 

[Cometborne]

Ooof, that does sound like a mess. It probably would be best to fork the project or start something entirely parallel. I think technically the tracker spreadsheet here is considered to be the most authoritative source of DSSA carrier info, so the plugin probably should have tried to use the sheet for its list of carriers. That's how I still populate the DSSA carriers for the EDAstro galmap too.

I'd be willing to put my money and time where my mouth is, fork the project, eat the cost for the server side, and then start hitting things with a big hammer. But as far as I am aware, the source for the server part is not public and relies on some kind of special framework from d3develop.com. If I try to reinvent that wheel, it is sure to come out egg-shaped, and the project deserves better.

I fully agree that both the server and client side of EDPS should be using the official tracker for data rather than hardcoded lists. Of course, there is the additional can of wroms that there are at least three "DSSA tracker spreadsheets" floating around, and they all contain different data. I have a script on my private FreeBSD box that downloads all of them, parses them, converts the information into csv format, and tracks that using RCS (yes, I am an adherent of the KISS principle). And this tracking of the trackers showed me that there is exactly one tracker that is reliably and quickly updated when a DSSA carrier owner updates their registration form, and that is the one given by Quohen in the first post of this thread: https://bit.ly/dssanetwork
This is also the only tracker that has all the DSSA carriers, including all the ones in pre-planning state.

 

[Orvidius]

Yep, that's the tracker sheet I was referring to. It's the one that the EDAstro map pulls from.

 

[Deleted member 240115]

Yep, that's the tracker sheet I was referring to. It's the one that the EDAstro map pulls from.

So why not standardize on the "official" spreadsheet from Qohen at https://bit.ly/dssanetwork for a "source of truth"?

Also, I'm assuming from the past posts this EDMC plugin we're talking about is related to some sort of DSSA "passport" that tracks people's progress on visiting all the DSSA carriers?

I know my FC's and some of the other IGAU FC's in DSSA have been visited by folks doing some sort of FC "tour" in the past.
That being said, I guess in order to fork/replicate this abandoned plugin, what's the end goal? Helping people keep track of their DSSA visit progress?

As for resurrecting the plugin, I'd imagine it wouldn't be terribly hard to change the data format into some sort of standardized JSON payload? At that point it could be shipped anywhere configured to take an HTTP(S) POST input.

 

[skycoog]

The second post in this thread states that to earn a permanent GMP entry, you need to be on station for at least two years.

Just for feedback I had planned on keeping the DSSA Gene Roddenberry in place for 2 years for GMP, even though I understood that the commitment for DSSA was only one year. I'm still committed to the two year plan.

 

[Orvidius]

So why not standardize on the "official" spreadsheet from Qohen at https://bit.ly/dssanetwork for a "source of truth"?

Since I'm already parsing it anyway, I might make a JSON copy of it available. Hopefully the data there will continue to remain valid, but of course there's always the possibility of the project changing maintainers and people losing their form links, etc. If I ever need to make manual overrides to it, those can be reflected in the JSON. Anyway, it's an idea.

Just for feedback I had planned on keeping the DSSA Gene Roddenberry in place for 2 years for GMP, even though I understood that the commitment for DSSA was only one year. I'm still committed to the two year plan.

Awesome! I think a lot of the carriers will probably stick around a lot longer, but I'm sure we'll lose a few along the way. Mine will probably stay out there permanently.