search

OpenSprites / OpenSprites-next

(shelved) OpenSprites - Share your Scratch scripts, costumes, sprites and sounds with the community!
MIT License
16 stars 5 forks source link

Delete account #65

Open towerofnix opened 8 years ago

towerofnix commented 8 years ago

Confirmation by email would be nice - and a no-activity requirement of a couple days or so like Scratch does might also be good. Input?

bates64 commented 8 years ago

But why would a user wish to delete their account other than also deleting their Scratch account?

I think it's worth, rather than email confirmation, asking for confirmation through Scratch comments. see below

towerofnix commented 8 years ago

Speaking of which, if you delete your Scratch account, OS should probably also 'delete' your OS account.

However - after an account has been deleted, what should happen to resources and collections? I think Scratch admins can automatically delete all uploads/creations that users on Scratch have made, but when a user deletes their own account the projects don't get deleted.. For example the account eshinobip was deleted but its projects weren't.

All that really happens is the account's user page 404s.

(Being banned is different - your profile doesn't get deleted but you can't log on.)

(This info is really just guesstimations, I've never been banned or had an account deleted before! :package:)

bates64 commented 8 years ago

if you delete your Scratch account, OS should probably also 'delete' your OS account.

We'd have to check that on profile access, I assume?

bates64 commented 8 years ago

I think we should make deleting act like banning - just with confirmation from the acc owner rather than an admin - however resources are still visible (e.g. somebody links to it, we dont want dead links).

I feel like "deleted" user's projects on Scratch's side is accidental.

MegaApuTurkUltra commented 8 years ago

I don't think it's worth deleting accounts - only hiding them, like we do with resources (speaking of that, I should add some more checks for deleted stuff :package:)

I don't think the ST ever truly deletes Scratch accounts either

bates64 commented 8 years ago

Sounds like the best method is to periodically check to see if a given Scratch user (that also has an OS account) returns HTTP 404.

Then we know that that Scratch user has been "deleted," and we can also "delete" (hide) said user too because to the end-user, they no longer exist.

jamesd-uk commented 8 years ago

Run a check every midnight on half the OS userbase, and the other half the next night?

bates64 commented 8 years ago

I'll assign @MegaApuTurkUltra to this - idk how cronjobs work

MegaApuTurkUltra commented 8 years ago

node-cron is great and does all things :package: