Oh and to do this, just tap anywhere near the top of the screen

And we have to expect that trend will continue. I haven’t tested frontier capabilities since April but I know for a fact my local drafters are producing far fewer obvious smells than I remember seeing in frontier outputs even just last year.

Current frontier is likely still detectable by an experienced engineer, especially if they’ve seen enough gen code to recognize the patterns, but might otherwise be indistinguishable from junior-level work. That is, I wouldn’t be surprised if the current frontier models didn’t output ANY giveaway “slop” code or outright hallucinations. Symptoms might be more abstract like inelegant architectural decisions, obtuse alg/structure selection, or design choices that demonstrate no grasp of overall objectives.

My point was that from a project maintainer’s perspective, quality is more a side effect, and there’s no effective difference between no AI and no detectable AI. The actual point of a no-vibecode policy is (A) to communicate expectations, ensuring contributors know their PR must pass a sniff test, that their name is on it, so blind PR submission is never a safe choice, and (B) to have a bulletproof policy to refer to in retrospect if ever issues relating to AI use in the project arise.

Default scroll-to-top behaviors on status bar tap (or re-implementations of it in multiplatform PWAs) are a common culprit behind random scroll to top behaviors reported for mobile apps in the past decade or so. Not sure if that’s what’s up but worth checking if that gives you repro.

Yet in principle the social benefit described (amplifying voices of the unheard) isn’t entirely out of reach for social media as a category, especially if we can escape the era of closed platforms. Open alternatives are still relatively new. There is a plausible future in which closed platforms are left behind and we become much more capable of keeping mass public manipulation in check.

BoTh SiDeS .… voting won’t work …. what “needs to be done”

Wow. Can you guys at least vary your scripts a little bit? And maybe don’t try to hit all the buzz phrases in a single comment. Your target audience never reads that far.

That’s pretty much the subtext of bans anyway. To guarantee undetectable use the contributor must treat gen code like a junior’s draft and refactor prior to PR. If it’s undetectable, the end result is the same from the maintainer’s perspective.

And it’s not a new approach. This has long been true for contributions containing “found” code; we define what’s allowed knowing we can’t actually enforce the rule against the most artfully obfuscated violations because, aside from achieving ostensibly the same result, having that tappable sign protects the project from a lot of BS down the line.

Agreed, I’m pretty used to security key unlocks and still wouldn’t want that friction on a personal device.

Also just for completeness, since I forgot to mention: enabling stolen device protection and findmy/mdm to enable remote wipe.

Disclaimer: I only use iPhones for security testing, so this is more from related literature rather than first-hand experience.

IIRC the hardening unattended reboot could offer is already covered better by options like disabling biometric unlock, security key 2FA, enabling lockdown mode, enabling advanced data protection, disabling iCloud, disabling USB accessories, and so forth. Also unattended reboot seems like an easy prank vector or foot gun to render a device permanently inaccessible (i.e., device always reboots immediately after pin entry) requiring recovery mode reset or restore to fix.

And surprise surprise, a quick check of posting history reveals no call to action during primaries, and often no mention of elections at all.

Only after primaries conclude does it become so imperative, suddenly, to convince everyone why not voting is the only virtuous choice.

How convenient.

“…15 days ago”

If similar to equivalent state regs, when access to customers residing in that market is gated by compliance and subject to lawsuits or ban, the first phase of business-side operations change is immediately setting up minimum compliance workflow like a special webpage coupled with countermeasures (like proof of residency; IP historically difficult in court but has been used successfully for state-specific age gating) and boundary testing cycles. With especially large markets, however, the overhead associated with maintaining multiple separate workflows fails the efficiency test and the workflows are merged, which is how everyone tends to benefit from pro-consumer laws like GDPR.