Alex Bit

[meeting notes with Omar and Greg] ~3 days after #9929 is done.

[notes from meeting with Omar and Greg] 1. first we do take care of #9929 (ETA: 21JUL) 2. then we work on bootstrapping #9930 starting 24JUL. ETA 28JUL. 3. Then...

Solution 1: hardcode top 20 email domains and validate against that list for typos. If typo, don't let the booker move forward with the booking. Solution 2: send confirmation to...

> With nice ux copy, the payoff is worth the slight friction, if turned on by cal owner. My proposed solution was NOT to introduce friction for booker. My solution...

That's a good one. Suggestion: "Confirm bookers email twice" might suggest that the cal owner should confirm that. Instead say: "Ask booker to confirm their email twice"

Also, is there any way for you guys to count how many times your confirmation emails get bounced? If yes, then after launching this feature, you can compare the bounce...

Adding more user-facing features comes at a cost of making the product a bit more complex. Also asking bookers to provide email twice is a little bit of friction. But...

this is impacting our customer and blocking a next.js migration. thanks for looking into this issue.

seems that the inferred rule has some syntax issues.

strangely enough, even though the code is in java, when i switch the picker in playground to kotlin and try to infer rule again, i can actually apply the inferred...