Viewing profile — RZelaya
RZelaya
HN member- Joined
- Sat, May 30, 2026, 7:28 AM UTC
- HN karma
- 173
- Public activity
- 28 items
- HN profile
- View on Hacker News ↗
About RZelaya
Recent public activity
-
comment
Comment #48465804
[dead]
-
comment
Comment #48395118
[dead]
-
comment
Comment #48387833
Once the Apple Silicon Macs came out, I converted my whole family from PC to Mac because the price to performance finally made sense. I'm the resident tech support for my family an…
-
comment
Comment #48376814
[flagged]
-
comment
Comment #48376759
[flagged]
-
comment
Comment #48376727
[dead]
-
comment
Comment #48376715
[dead]
-
comment
Comment #48373148
[dead]
-
comment
Comment #48372361
Good catch. Easy edge case to miss if you only test on QWERTY. I'll double-check the implementation, thanks for the heads up. update: You're right, this is a real bug. The Direct v…
-
comment
Comment #48371751
Thanks for sharing this. The "phase out the broadly-scoped Accessibility API and replace with narrower permissions" point is exactly the right structural fix. Right now developers …
-
comment
Comment #48370721
From what I understand Wispr Flow distributes directly from their website and doesn't ship through the Mac App Store, so they don't go through Apple's App Store review at all. They…
-
comment
Comment #48370431
Apple's built-in dictation works for casual use, but in my own daily use the typo rate was high enough that I was constantly going back to fix things, which defeated the point (wit…
-
comment
Comment #48369962
Same approach: CGEventPost with Accessibility permission. The wrinkle was that my App Store reviewer wasn't comfortable with how I was using AX permission for auto-paste, even thou…
-
comment
Comment #48369952
The direct version uses CGEventPost to synthesize the paste, which requires Accessibility permission. The App Store version writes to the clipboard only, so no AX permission needed…
-
comment
Comment #48369726
Handy looks great. More tools in this space is a good thing for people who need them.
-
comment
Comment #48369718
Fair points. The notarization-but-not-App-Store path was actually a workable middle ground in my case. Apple still gates security via notarization, but doesn't gatekeep the use cas…
-
comment
Comment #48369713
[dead]
-
comment
Comment #48369681
[dead]
-
comment
Comment #48369663
The paste-phase failures are exactly where most of my hard problems have been. App switching mid-paste, focus changes, slow-loading fields. It's an ongoing battle. Transcription hi…
-
comment
Comment #48369630
The acronym is unfortunate, you're not wrong. MITM here is "Moogle In The Machine" (the Final Fantasy moogle + machine learning), but the security-context joke is fair and I hear i…
-
comment
Comment #48369621
[dead]
- comment
-
comment
Comment #48369512
Fair. I run Nobara on my gaming computer and built a similar dictation tool there with no API restrictions, so the trade-off is real. For this project I chose both: App Store reach…
-
comment
Comment #48369493
Useful context, thanks. I hadn't realized Google was tightening similarly. Would be interesting to see how the rationales compare.
-
comment
Comment #48369487
I see, that's a really fair point. And I can understand that banking field example. So I can see why they're guarding against it. My disagreement was less with the rule itself and …