Live data from Hacker News

Apple rejected my dictation app for using the accessibility API

mitmllc.com

191–200 of 200 posts

Re: Apple rejected my dictation app for using the accessibility API

#191
post #130

Earlier quoted context omitted.

Wrong answer...

How so? The accessibility API which is causing data exfiltration here doesn't even exist on the web.

It also doesn't exist if you close the computer and take a walk in nature.

But we're talking about a case where you also want/need to use native apps. Not necessarily browser. Even if "it's the same" in this case, not all apps are equally viable as browser pages.

Not to mention performance/privacy/etc wise web apps are a regression.

Re: Apple rejected my dictation app for using the accessibility API

#192

Earlier quoted context omitted.

How so? The accessibility API which is causing data exfiltration here doesn't even exist on the web.

It also doesn't exist if you close the computer and take a walk in nature. But we're talking about a case where you also want/need to use native apps. Not necessarily browser. Even if "it's the same" in this case, not all apps are equally viable as browser pages. Not to mention performance/privacy/etc wise web apps are a regression.

> Not to mention performance/privacy/etc wise web apps are a regression.

Privacy-wise, web apps are also much better than native apps, less apis to exploit and also you can use an adblocker to kill tracking which as far as I know, doesn't exist on any mobile platform at the moment, even on GrapheneOS (I'm not talking about basic DNS shenanigans but actual automated native tracker removal)

I'd only agree about the performance part and even then, with the regression of mobile performance in the last few years (Material 3 / Liquid glass), it's not as clear cut as it used to be.

> But we're talking about a case where you also want/need to use native apps

Well if it's your only criteria then, the bar to get accepted in your average mainstream Linux repo is much much higher than any current mobile platform.

Re: Apple rejected my dictation app for using the accessibility API

#193

Earlier quoted context omitted.

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 version's auto-paste hardcodes the QWERTY keycode for V instead of translating for the active layout, so Dvorak / Colemak / AZERTY users would all hit it. The MAS version is unaffected (clipboard-only; the user presses their own Cmd+V, which…

Good luck. I’ve been building a native AI client[0] for the past 3 years and I didn’t catch this edge case until some of my users asked for it. [0]: https://boltai.com

[dead]

Re: Apple rejected my dictation app for using the accessibility API

#194
post #93

Earlier quoted context omitted.

I'm the IT guy to most of the elderly people in my life, and steadily switching them over to Linux Mint over the years. Fact of the matter is, most of them use their OS as a gateway to their web browser, and don't care to do anything else with it. For many non-technical users, switching OSes is literally a non-thing. The only difference vs Windows is that they call me for assistance way less frequently.

Are you upgrading their release for them every year or so once it becomes unsupported?

I put them exclusively on LTS

Re: Apple rejected my dictation app for using the accessibility API

#195

I actually had the almost same situation by building an offline voice dictation app for macOS and iOS, and in macOS I was confronted with the exact same situation. However, I would like to point out that Apple isn't totally wrong here because the accessibility API unfortunately is way too broadly scoped, and because of that you literally get access to everything on the computer like you you can screenshot listen and…

[dead]

Re: Apple rejected my dictation app for using the accessibility API

#196

Earlier quoted context omitted.

i think the issue is that you can still have these all under the accessibility api but why not break that down more accessibility.screenshot accessibility.paste and whatever else there is. that completely removes the issues for apps like this.

As a programming practice in service of the principle of least privilege, that would make complete sense. The issue is with Apple's UX. Apple insists on asking permission for every little capability an app wants. So I would have to say "yes, allow this app to take screenshots" and "yes, allow this app to read the clipboard". I wouldn't be surprised if, in the near future, Apple forced people to click "yes, allow this…

annoying true, but no reason they couldn't group read/write into the same prompt.

Re: Apple rejected my dictation app for using the accessibility API

#198
post #124

Earlier quoted context omitted.

I commented on BrownHairedGirl’s RFA. The most toxic user ever on Wikipedia. I can assure you, there are those on Wikipedia who committed far worse offenses and they remain. Like I say - a cesspool that doesn’t respect article writers.

Were you Chris.sherlock/Aussie Article Writer on Wikipedia? Sounds like pot calling the kettle black re: toxic. You had an interaction ban against her FFS. https://en.wikipedia.org/wiki/Wikipedia:Administrators%27_no...

And why was that interaction ban enacted? It was immenseley unfair. It was pathetic in fact, given it was a one-way ban, and she had consistently denigrated me. Unless you think that's justice.

So no, not the pot calling the kettle black in any way. She had her coiterie of followers, and she was banned as a bully. They enabled her.

Re: Apple rejected my dictation app for using the accessibility API

#199

Earlier quoted context omitted.

I commented on BrownHairedGirl’s RFA. The most toxic user ever on Wikipedia. I can assure you, there are those on Wikipedia who committed far worse offenses and they remain. Like I say - a cesspool that doesn’t respect article writers.

Ah, I see, you were instigating constantly and people were sick of your shit. Seems like a reasonable ban, especially when you violated an IBAN already.

How was I instigating constantly, Chris? Can you provide any evidence of that? Perhaps an ArbCom investigation?

You can't, because that never happened.

But hey, keep defending BrownHairedGirl. You seem to be fine with her constant abuse!

Re: Apple rejected my dictation app for using the accessibility API

#200
post #125
post #102

Earlier quoted context omitted.

This comment is a little light on the reasoning for why you were permabanned.

Someone did the research-digging a while back about this, if you want a third-party view: https://news.ycombinator.com/item?id=45136376

Indeed. The person who responded made the following points:

* BHG then made a thuggish and threatening post on your user page:

* BHG later characterised this like "oh but he was trolling me and I merely asked him one time on his talk page to stop (which is allowed)", which is bollocks because the "one time" is a long, angry screed written in a menacing tone.

And yet, no action was taken against her. I wonder why that was? And yet I was the one who was indefinitely banned. There was clear bias, and Wikipedia lost a good contributor. One I would say did far more than she ever did (she dealt with categories and dead links, and one article relating to Ireland).

Incidentally, if you want to know what the poster missed... it was that it was a one-way interaction ban. BHG was never, not even once, admonished for the way she treated me. In fact, her supporters actively encouraged her to attack me. When she attacked me, I was unable to defend myself or respond. Does that sound like procedural fairness to you?

Funnily enough, she did this to one too many people and was banned. I was banned by her supporters, not by ArbCom. It's what is known as a kangaroo court.

But hey, fairness and impartiality on Wikipedia was something that was lost a long time ago. Wikipedia is continuing to slide into obscurity. The ones who are active are most interested in drama, and not content. I feel sorry for those who are there for the content.

Post reply on HN