[Discussion] SWAN v2.0 FOR REAL

Sounds good. I think that area’s a bit outside of my experience so I’ll leave the architectural decisions to you, but if there’s any areas I can help with coding, just let me know.

To circle back to some non-technical areas that you brought up in your initial post:

  • You’re definitely right that the ping dispatches can be improved. I also like the concept, but some areas (e.g. ‘voting in Local Council elections’) are showing their age.
  • Cards for awards winners sound like a good idea. There are probably others better positioned to judge how the first month of SPACE went though :stuck_out_tongue:
  • We could have a factbook/dispatch template or some way for people to show off their awards. I’m not sold on that, but maybe it would help make getting an award feel more special if there was an easy way to show off those awards, compared to just getting an image to download?

Does Trove maintain the DB by itself or is there an external script to do it?

You’re right about the award thing. I am not a design expert though so someone else will have to figure it out.

Seems like there’s some scheduling code here, but I’m not really familiar with PHP or the frameworks Glen used.

For the awards, I can do some BBCode finagling and see what I come up with, though no promises about my design sense either :stuck_out_tongue:

1 Like

Yeah. Trove definitely does download and parse the data dump by itself, it is in the Console/Commands/ folder. It seems to convert the dump into CSV files then ask the DB to import the CSV files. Never understand why we had to use PHP for this. If it was in Express, NestJs, or anything in the JavaScript/Python space I would have been more interested in maintaining it lol.

Having an API to get fancier data is actually convenient since some of our stuff may use the same kinds of data that need further processing. I imagine we can have separate cron scripts to maintain the DB and analyze the endo data and store the result somewhere. We then have an API to access that data (for endotarter tool, dispatches, or even a web tool to view the data)

Yeah, agreed on the API point. I am probably getting ahead of things here but I think there are a few different tools/services that could use data which could be stored in a common database (endotarting tool, endorsement data, or this thing that’s still in Private Halls for now, etc.).

1 Like

Hey Proboun, it’s oscar the coder who chatted to you in DM’s. as you know I am an experienced python coder and I’m willing to help with this

It’s been a while. Recently, TNP’s endotarting tools went down and I know at least a few of us were using them, so I figured I’d poke the topic to see if we couldn’t bring some of that functionality back, or otherwise keep making progress on the ideas listed in the OP.