Post · Indieweb Studio

Post

dansup

@dansup@mastodon.social · 5 days ago

Me: oh yeah, implementing Loops Admin Invite urls will be easy

*2 hours later*

Only finished the admin dashboard + backend.

Still need to wire up the frontend 😅

(It would have been done already if I didn't add auto follows and admin email alerts)

#Loops #LoopsDev

dansup

@dansup@mastodon.social replied · 5 days ago

I'm using uuid v7 for the invite_key because the AdminInvite model supports soft deletes with a unique constraint to retain the invite id in the users model while hiding "deleted" invites.

I spent way too long deciding on the invite_key format, and prepended it with `a_` to denote it's admin generated in case we allow user invites in the future and need to differentiate due to other constraints (like closed registration, user invites won't work, but admin invites will)

Heliograph

@Heliograph@mastodon.au replied · 5 days ago

@dansup wouldn't "a_" be too generic? (for the long haul?)

dansup

@dansup@mastodon.social replied · 5 days ago

@Heliograph "a_" is just to denote is admin generated, we can use anything else for future invites, but they are likely going to be just user invites, which can start with "u_" for example.