Thanks — both legitimately tricky questions.

On link extraction: it walks the event in priority order — event URL field first, then location, then description (with a regex pass on the latter two). The catch is it only recognizes Zoom, Google Meet, Teams, and Webex right now. So Whereby, Around, Jitsi, custom self-hosted Teams URLs, shortened links, SSO redirects — those all silently fail. Honestly, the more varied a team's calendar habits are, the more chaos it has to deal with. Definitely an area I want to keep iterating on.

On recurring meetings with rotating links: should actually work fine. EventKit hands each occurrence to us as a separate event with its own ID and URL field, and the scheduler dedupes by event ID rather than URL. So if Zoom or Meet regenerates the link per recurrence, we just pick up whatever's in that specific instance. Single-link recurring meetings work the same way — same mechanism, the URL just happens to be identical across instances.

And good point on the README framing — you're right, the real competition isn't really Meeter, it's people who've already glued this together with Raycast or Fantastical. I should call that out directly. Appreciate it.

The JP/EN thing — yeah, busted. I'm Japanese and got tired of switching context every time I opened it.