User Details
- User Since
- Jul 20 2020, 4:28 PM (280 w, 3 d)
- Roles
- Administrator
Yesterday
This was landed, but it got squashed into another commit due to the way we handled the corresponding GitHub PRs (Phabricator was down at the time, so we used GitHub)
This was landed, but it got squashed into another commit due to the way we handled the corresponding GitHub PRs (Phabricator was down at the time, so we used GitHub)
Mon, Nov 17
Thu, Nov 13
Wed, Nov 12
Discussed in 1:1; @kamil will follow-up with responses to my comments later
Nov 4 2025
Nov 3 2025
Oct 31 2025
Oct 30 2025
This one is hard to review... I'm not really familiar with the .pbxproj format. Regarding the notification service limits, I'm not familiar with those either...
Oct 29 2025
Oct 28 2025
Oct 24 2025
Oct 23 2025
Makes sense!
D15516 fixes the issue I was referring to.
Here's a failing unit test: https://linear.app/comm/issue/ENG-11509/messages-appear-as-if-from-wrong-user#comment-94575408
We have an object that looks like this:
These buttons not having a loading status was a pet peeve of mine. Thanks for fixing!
I am skeptical of this approach. The core issue is that our FID extraction breaks when unexpected object fields are encountered. What happens if Farcaster introducing a new object field? Won’t the same issue occur? I think we need to fix the core issue instead of reverting this. Let me know if I’m missing something.
Oct 22 2025
Oct 21 2025
Oct 20 2025
We need this for CORS requests