User Registration

[miawinter98]

Potentially with option to disable signup (i.e. environment variable and/or admin api endpoint)

[mstarongithub]

Important question here would imo be what methods we want to support. Probably Username+password(+totp), and I think passkey alone should also be an option (auto-discover and all that jazz, mostly backend stuff that I already have (probably) working in Linstrom

[miawinter98]

I am a big fan both of simplicity (email+password) as well as passkeys

Totp also always good, just have to make sure the api responses on login support the frontend flow there of "enter email, password", submit, "ask for Totp code", submit, logged in

[mstarongithub]

my approach in Linstrom is to send a flag response back after the first action, telling the frontend which state it should go to next (auth success, auth failure, totp required|passkey required). Also included a token, either for tracking which login it was or for the frontend to then use to authenticate

[mstarongithub]

Another question is what user data do we need at what point. Registration is username+email (+password (+totp verification) / + passkey verification / +oidc connection). For day to day usage probably events/calendar entries (what info for this is yet another question)

[miawinter98]

For MVP I would just do email and password

Also no usernames, I feel in this day and age, unless you make like a social media, it's unnecessary and clunky. Rather do a display name later for personalization. But since this is a calendar app everything is usually done for emails anyway (appointmentees, organizers, etc.)

[miawinter98]

Calendar entry discussion I would do in the caldav issue and after getting my head around the standard. No sense in inventing a database scheme when the standard already has a certain structure in mind (since it's an extension to webdav, probably something folder-like)