sinwell

Guess I’ll just pin this to the board with all his other Lemmy TOS violations

deleted by creator

Yo, this you?

Guess it’s just a coincidence that you guys created accounts at the same time, show up in threads together, vote together, and talk the same.

Speaking of which, your most damning tell is pushing this “Reddit agents” conspiracy to indiscriminately accuse every critic of “shilling” without evidence other than how they dared to call you out (for anything, apparently: undisclosed botting/spam, copy-paste reshitposting, blatant misogyny and racism, etc.) then banning them from communities your alts moderate, deleting their comments, and reporting them for harassment.

Now that you’re using AI to write your comments, you might think no one can trace you across all your botting alts because your characteristic language errors are papered over, but you’re wrong.

In reality, most of your alts are already linked by your own childish threats, ban evasion minging, impulsive chest-beating, and accidental persona-hopping in various argument threads. Like, here you are threatening to ban a user from your fiefdom using the wrong account:

But even if you hadn’t already repeatedly exposed yourself or feebly lied as you just did, and even though you never disclose any of your botting alts playing victim when called out, and even if Lemmy weren’t a small town to Reddit’s metropolis where your abuse was a raindrop in a torrent… anyone who looks twice can tell it’s you.

Seriously, quit all this bad-faith brigadier botting bullshit and get your ass into therapy. The incel and white supremacist Reddit content you’re compelled to dump here is toxic waste that is poisoning you.

The only “Reddit game” being played here is yours and you’re playing yourself.

This looks like a Mexican (or maybe SA) gated residence. There’s generally less distinction made between inside and outside. Only some parts of the house are deliberately sealed for HVAC. But it’s an afterthought. The original architecture was designed to encourage airflow. This part of the house for example is an open corridor that the wind blows through. And yes, the property has been gradually expanded by local smalltime contractors, probably friends.

Well the idea is to NOT say “make it indistinguishable” (even if that’s inevitably the practical upshot) because the second you explicitly allow “indistinguishable” you open a can of worms arguing over what that means.

The same result unfortunately seems to be found by any attempt seeking this “middle ground,” because there’s always a cohort implicitly requesting that project maintainers bless their low-effort use of AI. (As to why this is, I’m not sure, but based on what I’ve seen would guess it’s because the AI use lets these individuals cosplay as developers.)

Regardless, that result is a huge influx of PRs which have obviously been submitted by individuals incapable of understanding, fixing, or taking responsibility for what they’ve submitted, which is an immediately intractable problem for project maintainers who already began with limited time to review PRs which, in spite of their varying quality, could at least be assumed to be understood by the contributor. Allowing any amount AI enables some amount of obvious (read: unfiltered/unreviewed) generated code, every bit of which is potentially problematic.

Former* friend

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.

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.

deleted by creator

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”

I assume they mean the GF is referring to puncturing the pleural lining to give the corpse a collapsed lung.

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.

Yay! Happy for you OP!

Bobby, if you weren’t my son, I’d hug you.

Oh shit. I’ve been trying to put to words what I find so obnoxious about tankies and you just nailed it.

Before you go go whoops didn’t see post body