taco

I was joking, but it was my actual thought process when I responded to Google’s email about this by deleting my Play Games profile altogether.

Also, I haven’t played a new Android game in years.

My Steam history isn’t intimately tied to my bowel movements though. This is more personal.

Pirate everything, and share as much as you’re able.

Small fires can prevent larger ones in the future.

Weekday drinking as a hobby.

What’s wrong with a time tracker?

I’ve worked in once place where I was support (no projects, all work came from and was tracked in tickets). Since everyone had to use the time tracking system anyway, I had to enter 8 hours every day. I was salaried, so no OT or docked pay for time off; I entered the same 5x8 every week, regardless of what or when I worked that week. Pointless.

Another time, I was subcontracting and had to enter time for the same projects for both my employer and the company that hired us. My employer wanted time submitted twice a month, and the hiring company demanded weekly. Tedious.

Two of these three companies were irrationally anal about pre-filling the time sheets, even when the hours were well planned or functionally irrelevant.

Arr, ye be wantin’ the secrets o’ the Servarr fleet, eh? Then lend me yer ears:

Sonarr – This be the lookout in the crow’s nest, keepin’ watch fer new episodes o’ yer favorite shows. When it spies ‘em, it signals the crew to fetch ‘em down from the digital seas.

Radarr – Aye, this one’s the treasure hunter, scourin’ the oceans fer full-length films instead o’ episodes. It marks the map, finds the booty, an’ brings the shiny reels aboard.

Lidarr – The ship’s bard, huntin’ down new shanties an’ albums to keep the crew’s spirits high on long voyages.

Readarr – A learned scribe, fetchin’ tomes an’ scrolls fer them what likes a quiet night with words instead o’ waves.

Bazarr – The translator, givin’ ye subtitles fer shows an’ films in whatever tongue ye fancy, so no sailor be left in the dark.

Prowlarr – The scout, integratin’ all yer trackers an’ indexers into one mighty spyglass, so the rest o’ the crew can search the seas more smartly.

All together, they be runnin’ like a well-oiled pirate crew, each wit’ a role in findin’, organizin’, and keepin’ yer plundered media shipshape.

This stands today as my favorite demonstration to show people why I’m so grumpy at their meeting invites. Thank you for posting it here, as it was my first thought when seeing the OP.

This is the answer. Much more reliable than the killswitches.

The committed code in the repo will get scraped anyway, but the data used in testing is a different story. Not that anyone’s ever tested with prod data.

I don’t think the issue is a practical one though. It’s more the company that stands on promises of privacy using tools that are overtly share-happy that seems to be a ideological discrepancy.

But in case my initial comment’s “I don’ think…” wasn’t clear enough, this was my attempt at understanding why this might be a concern (or at least of interest) to folks in this community, not a personal statement of condemnation or anything. I personally could not give less of a shit what code editor they use.

I wasn’t shitting on anybody. You’re ranting is misdirected.

I don’t think the concern is as much with the purity of their vibe coding, but rather that they’re using an AI-first editor. This will almost certainly mean everything they’re coding is being shared with AI provider(s) during the process, which some would view as at odds with Proton’s stated emphasis on privacy.

Google has 182k employees as of 2023 (at least according to Wikipedia). There’s no way to have that many people and not have one slip up once in a while.

Yes. It may deflect some of the legal responsibility, but it’s still more of a “how they got breached” than “they didn’t get breached.”

Which is exactly why it overheats so quickly when they close the lid.

Let’s face it, the place using a laptop on the floor with a paper sign probably doesn’t have the budget for real sysadmins. At the same time, most real sysadmins know to disable the lid-closing behavior and get the laptop off of the carpet because they’ve been foiled in their past by people who refused to read the goddamn paper sign.

Reminds me of the pettiness during the aftermath of the class action because of the Nexus 6P battery problems. Google/Fi suddenly lost all records of my support tickets, my having purchased the phone at all, the warranty replacement they’d done, etc.

Fortunately, I keep meticulous records and still had a phone that powered down at 60% battery, so recorded a video of it as evidence and got my payout. Severely tainted my impression of Google/Fi though. Neither the faulty hardware nor the shady practices are surprising at this point.

I don’t think an article writing for an audience that needs API defined is the place to get the finer details. Also, does it really matter? Keeping secrets out of the repo is pretty basic stuff, so there’s a lack of fundamental information security awareness.

I’d bet all the monies that there’s a bunch of unencrypted spreadsheets with enough data to steal millions of identities on some idiot’s Google Drive or whatever, and a bunch of it’s been shared with commercial LLMs without any of our consent. Our personal data’s being handled less securely than the average corporate SharePoint site’s plans for the next pizza party.

I meant actual data. You’re refuting a claim backed by several cited studies in the OP.

Have anything behind that? The paper we’re discussing has 4 citations in agreement, so I’m not so sure that most people say the opposite.