VITAS changed the topic of #spacedock to: Problems?: https://github.com/KSP-SpaceDock/SpaceDock/issues | Matrix/Riot Chat: https://im.52k.de +spacedock:52k.de Feel free to ask for help, we only bite a little bit! | If you want to help, please check https://github.com/KSP-SpaceDock/SpaceDock-Backend/issues/5 :) | <VITAS> inet users have the attentionspan of a squirrel...
VITAS[m] has quit [Quit: Idle timeout reached: 10800s]
KineticSloth8StoneBlue[m] has joined #spacedock
<KineticSloth8StoneBlue[m]> can I check the CKAN box at *any* time, after publishing a listing, for it to do its thing?
<KineticSloth8StoneBlue[m]> or does it have to during the initial listing?
<KineticSloth8StoneBlue[m]> can I check the CKAN box at *any* time, after publishing a listing, for it to do its thing?
<KineticSloth8StoneBlue[m]> or does it have to be during the initial listing?
HebaruSan[m] has joined #spacedock
<HebaruSan[m]> Anytime.
<KineticSloth8StoneBlue[m]> Thanx!
HebaruSan[m] has quit [Quit: Client limit exceeded: 6]
KineticSloth8StoneBlue[m] has quit [Quit: Idle timeout reached: 10800s]
VITAS[m] has joined #spacedock
<VITAS[m]> if we delete users that have published mods. What happens to the mods?
DasSkelett[m] has joined #spacedock
<DasSkelett[m]> We should delete them, that's what the user would expect.
<VITAS[m]> i feel sad when (genuine) mods get deleted
<VITAS[m]> but i supose youre right
<VITAS[m]> i wonder if soft delete would be a way
<VITAS[m]> im torn
<DasSkelett[m]> As in, just remove it from the database, but keep the files?
<VITAS[m]> i feel like i have a responsibility as curator of ksp mods
<VITAS[m]> as in flag the row in the db as deleted
<VITAS[m]> and not delete it
<VITAS[m]> only for mods not for users
<VITAS[m]> but that could cause problems if we ever implement foreign key constraints and have cascading
<VITAS[m]> i would like to somehow preservere a copy and the metadata
<VITAS[m]> but not publicly
<VITAS[m]> but on the other hand i think i should respect the authors wish of removing it
<DasSkelett[m]> We already have several foreign key constraints and relationships between mods and users, so deleting the user row but keeping the mod and mod version rows would definitely not work and likely throw a lot of exceptions.
<VITAS[m]> whats more important? preserving for the future many or removing for the creator?
<DasSkelett[m]> I guess in the end we have to do what your favourite topic, the GDPR says.
<VITAS[m]> is there a question we could ask the author when publishing stuff?
<VITAS[m]> but who would check a box á la "i dont want this mod to be deleted even if i press delete"
<VITAS[m]> ive to think a bout it and maybe offer a discussion ont he forums
<VITAS[m]> i think the minimum would be to have an "disable / unpublish mod" for the author
<VITAS[m]> so he can chose if he wants to take it off the air or rely purge it
DasSkelett[m] has quit [Quit: Idle timeout reached: 10800s]
VITAS[m] has quit [Quit: Idle timeout reached: 10800s]