10:09 <VITAS[m]> im a bit upset that curse is still first when you search "ksp mod" on that search engine

10:09 <VITAS[m]> ideas how we could out SEO them? :D

10:11 <VITAS[m]> that reminds me: would it be doable (performance wise and technicaly) to use matomo/piwik as source for dl stats and only show them to the mod authors? i think that normal users only need to see the total download count

10:12 <VITAS[m]> we could offer mod authors more detailed insigts e.g. os usage

10:12 <VITAS[m]> or screen res

10:13 <VITAS[m]> (and yes i know you can block matomo. but all tracking would have to be blockable)

10:15 <VITAS[m]> similarly: could and want we generate suggested mods from matomo stats that could give us an idea what other users where downloading after downloading/viewing the same mods?

10:15 <VITAS[m]> just like yt does it

10:29 <VITAS[m]> and another idea: should we offer ckan on spacedock for download?

11:22 <DasSkelett[m]> CKAN has currently multiple release assets on GitHub, for different OSes and Linux distributions. Though we could restrict the SpaceDock entry on the simple exe for the Windows users.

11:22 <DasSkelett[m]> I would like to have the opinion of HebaruSan and the other team members first.

11:30 <VITAS[m]> or you could detect the browser os

11:30 <VITAS[m]> ckan isnt a mod

11:30 <VITAS[m]> im thinking about its own menu entry

11:30 <VITAS[m]> and page

11:31 <VITAS[m]> said menu entry should only visible in games that ckan supports aka ksp

11:34 <DasSkelett[m]> That would need a lot of if-elses until we have covered all the distros using a certain packaging format.

11:38 <DasSkelett[m]> Offering the different packages side-by-side so the user can download what he needs and wants would be better in that regard, but this would basically need implementing https://github.com/KSP-SpaceDock/SpaceDock/issues/217 which I don't want to, since it will mess up CKAN's indexing massively.

12:41 <VITAS[m]> youre still thinking about ckan as a mod?

12:42 <VITAS[m]> just check if ckan is available for that game (i think we have a flag in the db for that) then add it to the navigation as link pointing to a semi static page that offers links to downloads

12:43 <VITAS[m]> (it should ofcause offer some explanation what ckan actualy is)

12:45 <VITAS[m]> github might have a mechanci to auto populate /update that ckan page on sd with new releases

12:46 <VITAS[m]> bonus: you can add a link to that page from any mod on sd that is listed on sd (just link the ckan pill/button in the mod details)

12:46 <VITAS[m]> thats my offer :)

13:53 <DasSkelett[m]> Dynamically updating the page sounds like a lot of work.

13:53 <DasSkelett[m]> The way I can think of doing this is by adding a webhook trigger to CKAN's repo, that triggers a new webhook of SpaceDock after new releases, running a script that fetches the latest release information and download links from the API and filling them in into the page template.

13:53 <DasSkelett[m]> Better alternative would be letting the clients do the API call in JavaScript and fill in the page I guess.

14:01 <DasSkelett[m]> To keep you all up to date what happens on the other side.

14:45 <VITAS[m]> i should investigate if setting up my own bridge would help

14:46 <VITAS[m]> so uploading for balsa wont work as a of now ?

14:47 <VITAS[m]> i added balsas version to the db

14:48 <VITAS[m]> what needs to be done from your sides to be ready to update prod?

14:50 <DasSkelett[m]> Yes, no Balsa uploads. This PR fixed it: https://github.com/KSP-SpaceDock/SpaceDock/pull/271

14:53 <DasSkelett[m]> I need to cherry-pick one fix that isn't in beta yet, then I / we should test every important function again. I'm ready from my side then.

14:55 <VITAS[m]> ill ask if someone wants to help test beta.spacedock