@beebrookshire I've always found it stupid that we lose our baby teeth as babies instead of maybe late teens. After we've had the chance to screw them up a bit and hopefully learn the lesson.

@mcc my first thought from a security perspective was to have all local data wiped and replaced with {user}'s data on login, or potentially segregating it by auth'd user locally (trusted shared device). Both of those break the offline-online flow for anything that's not synced yet so my next issue is do I automatically assign anything local to {user} when they log in, or should I ask for each item if they want to sync or delete?

Idk if paper to digital forms are an upgrade sometimes.

@mcc slightly different since its effectively an app rather than a website but this is something I'm trying really hard to avoid in the thing I'm building now.

Basically making it "offline first" store everything locally and try to sync in the background if you're logged in. Adds the user ID on backend when syncing with proper auth.

It's more effort but it would be nice to see people care about UX more.

@cmthiede @Natasha_Jay in this case I thought what they're paying for was mostly plausible deniability and blame shifting when investors find out that the numbers you showed them were 20x better than reality.

@gabriel @alice an argument I've seen before is "you aren't your type", which I think can help for people who don't see themselves as attractive even though they probably are plenty of other peoples' "type".