Handling deleted user attendance data

[ankitshah811]

How can we prevent this from happening? Very frustrating.

[nickbarnwell]

That's not a bug, that's a deleted user.

[ankitshah811]

@nickbarnwell How is the user deleted? Users can't delete themselves rn (I know that's poor practice, but I removed that functionality for time being), and we didn't delete any users after 25 September, did we?

/ can we make it so that a deleted user doesn't occupy the spot of someone who could come off the waiting list?

(also apologies if reopening issue here was not the best practice. Not sure how to best approach this.)

[nickbarnwell]

They could have deleted themselves by manually calling the route. Not out of the question for a technical user. As for the not taking up a spot, you need to think through what we should actually do with deleted users, how to handle disabling v. permanent deletion of an account, etc.

On another note, please stop posting screenshots with PII to the issue tracker! Your future legal department is crying right now!

[ankitshah811]

LOL I often forget this is all public. Thanks for the reminder.

How I think this should work —

1. User's past tea time attendances should still be marked as [Deleted User] with attendance_status as whatever it was beforehand.
2. User's future tea time attendances should be marked as [Deleted User] with attendance_status = flake

Would we be able to commonly identify a Deleted User as being the same one as another Deleted User? For example, can we pinpoint whether or not Benny's two tea times have the same person who deleted their account marked as attending? (i.e. DeletedUser42 as opposed to the universal DeletedUser)

Still baffles me how somebody deleted their account, as there are 2 instances of future tea times with a deleted user marked as attending / 1 future tea where deleted is marked as flake. Is it a URL they'd go to? Or would they need to use dev tools?