<Darklight[m]>
It's more likely that they are getting notifications and want it to stop
Darklight[m] has quit [Quit: Idle timeout reached: 10800s]
ValiZ0ckt[m] has joined #spacedock
<ValiZ0ckt[m]>
If I may still join this small discussion I’d say yes, they won’t be updated anymore and stay in the the state the modder leaves. Dealing with old mods is always annoying (support wise)
VITAS[m] has joined #spacedock
<VITAS[m]>
its more about: what happens if an account or mod is deleted
<VITAS[m]>
do we just make it invisible so we can archive it for the future (think about retro games and ksp certenly will be a classic)
<VITAS[m]>
the pros for deleting are ofc the modauthors trust in us removing data if he requests it
<VITAS[m]>
this discussion is NOT about distributing mods that are flagged as deleted
<VITAS[m]>
its purly about do we Archive mods for future generations
HebaruSan[m] has joined #spacedock
<HebaruSan[m]>
Do mod files get deleted out of storage at all currently, even if deleted by the author?
<HebaruSan[m]>
It's possible to mark the mod and modversion as deleted without touching those files
<HebaruSan[m]>
And also to stop providing them for download
<HebaruSan[m]>
And yet they could still be there on the server
<VITAS[m]>
yes flagging files is what i call soft delete
<HebaruSan[m]>
Future generations would probably be OK with that
ValiZ0ckt[m] has quit [Quit: Client limit exceeded: 6]
<DasSkelett[m]>
I'm not sure how well the database If we want to keep the mod data in the database, we'd also have to keep the user row I think, since they've a relationship.
<DasSkelett[m]>
If we want to keep the mod data in the database, we'd also have to keep the user row I think, since they've a relationship.
<DasSkelett[m]>
Taking a look at cascading deletion, depending on how we're going to implement account deletion it might help us (and it would simplify a bunch of already existing code)
VITAS[m] has quit [Quit: Idle timeout reached: 10800s]
HebaruSan[m] has quit [Quit: Idle timeout reached: 10800s]
VITAS[m] has joined #spacedock
<VITAS[m]>
yes if we do soft delete all has to be soft delete
<DasSkelett[m]>
Then there's everyone's favourite topic, the GDPR, again. While we might be allowed to keep open source mods, AFAIK we aren't allowed to keep any user data. No one knows how user data is actually defined, but a row in a database probably falls under it.
<DasSkelett[m]>
Maybe we could strip the db entry from all information (user name too?).
Darklight[m] has joined #spacedock
<Darklight[m]>
I don't think I have any input on this one, apart from maybe consistency - I believe deleting a mod from spacedock does an actual delete, we likely should do the same for user accounts
<DasSkelett[m]>
(see the code I posted above, we do)
<Darklight[m]>
I'll reiterate that it's most likely a user requested thing rather than a modder requested one, because I don't think we have a "hey stop sending me emails please for all these mods I subbed to" button
VITAS[m] has quit [Quit: Idle timeout reached: 10800s]
DasSkelett[m] has quit [Quit: Idle timeout reached: 10800s]
Darklight[m] has quit [Quit: Idle timeout reached: 10800s]
VITAS[m] has joined #spacedock
<VITAS[m]>
i think we allready went down this discussion
<VITAS[m]>
the only way i can think off is to somehow dump the description and maybe username and date into a textfile and archive it in a different place
<VITAS[m]>
(e.g. different folder)
<VITAS[m]>
gdpr only applies to user related data
<VITAS[m]>
mods arent that
<VITAS[m]>
but userdata is (e.g. email address)
DasSkelett[m] has joined #spacedock
<DasSkelett[m]>
This would also be my preferred approach. And do it on upload, not deletion, and all the problems are solved.
<VITAS[m]>
yes so question: could you autogen such meta files in the mod folder for each mod on upload and for the existing ones?
<VITAS[m]>
it should contain stuff like license, author, date of upload/creation, description and maybe a checksum of the zip
<DasSkelett[m]>
I.e. CKAN metadata files
<VITAS[m]>
i can implement rsync to mirror mods
<VITAS[m]>
whatever floats your boat
<VITAS[m]>
ckan is allready defined so good idea
<DasSkelett[m]>
Anyways to get it moving forward and not spend the entire time discussing how and when and what: