Blauerdaemon

Firefox 51 and Chrome 56 display insecure password warnings if login pages are non-https. See https://support.mozilla.org/en-US/kb/insecure-password-warning-firefox So this issue starts to become more visible for the average user.

Activating HTTPS in IPS seems simple. At the start of the linked page it is told how to activate it for parts only but below the first image there is a section about moving to 100% HTTPS. Obtaining and setting up a certificate might not be trivial but at least with Let's Encrypt it should not take much time. A possible direct benefit for Squad apart from appreciation by the users would be that HTTP/2 support by browsers is better with SSL/TLS - possibly reducing traffic costs.

@politas Actually it seems better to implement a central API for submitting change requests to the index than putting this in this Tool. Submitted an issue concerning this on https://github.com/KSP-CKAN/CKAN/issues/1857

@politas Skipping empty install now (since https://github.com/janbrohl/ksp-ckan-metadata-webtool/commit/4b46d08bbc57fde5c46d24bd5a660d7ce593c9c5 ) While of course it is possible to generate PRs directly demonstrated in https://github.com/janbrohl/NetKAN-API I do not see a big advantage in that which would be worth the trouble of authentication - maybe I am overlooking something. @kcs123 Thanks - I actually forgot to follow my thread (thought that would be automatic)

I am looking for feedback on a Webtool trying to simplify making CKAN metadata (more exactly netkan files). Please try it on https://brohlsoft.de/apps/metadata-webtool/ and tell me what you think - here or in the issue tracker. You can find the sources at https://github.com/janbrohl/ksp-ckan-metadata-webtool If you want to have a look at the CKAN index, you might like https://brohlsoft.de/apps/ckan/ too

Sure, PM me as much as you want. I am glad you want to help. The current version generates a netkan file and enters it in a github-issue for you. Then these would be added to the netkan-index by one of the CKAN people. Generating a complete pull request from the tool is planned (so the CKAN people would just have to OK it) but not yet implemented. If you want you can try a slightly outdated testing/preview version on https://ksp-ckan.github.io/metadata-webtool/ I just want to mention that I am not a member of the KSP-CKAN team so nothing I might say should be regarded as "official" in that area.

Bill (William) and Bob (Robert) don't sound bad to me for english names.

The current version crashes for me if not started via steam so id like to have a totally steam-less version, too. Now i have to wait until steam is done starting and then start KSP from there - precious minutes are lost. This GOG-action seems to be initiated by the GOG-people so it should be not much work for Squad to add KSP apart from telling them its OK, I suppose. For the other cross-adding I'd think there need some coding and stuff to be done.

I have just seen that you can add games from your Steam-library to your GOG.com-library for free - do you know if this this is planned for KSP, too?

Started working on a tool to help create (later also edit) CKAN-entries. Have a look at https://github.com/KSP-CKAN/metadata-webtool

@cybutek Are version files with additional entries (not just those mentioned in the "Version File Breakdown") still valid? Would you say that this JSON-Schema correctly describes a Version file's contents? https://gist.github.com/janbrohl/c614d2b4a2aee805d93428a2cbc44df5

Anyone still using this?

Mechjeb Embedded Universal 1.3 is now listed in the CKAN for both - career mode and free @Dennis6492

I made CKAN-files for 1.3 and it seems to work fine with KSP 1.1 for me. Submitted at https://github.com/KSP-CKAN/CKAN-meta/issues/1096

@SirCmpwn Thank you for your great work!