2026-07-18 06:44 UTC
Replies (7)
-
@MartinaNeumayer@mastodon.social 2026-07-18 06:59
@daniel@gultsch.social I hope you send them back the only one response possible:🖕 #FuckGoogle
-
@Oleksii@social.linux.pizza 2026-07-18 07:41
@daniel@gultsch.social @bagder@mastodon.social have you got the same?
-
@pankraz@freunde.ma-nic.de 2026-07-18 07:40
@daniel@gultsch.social So the generated code has the same license, right? Right?
-
@guenther@chaos.social 2026-07-18 08:29
@daniel@gultsch.social Is this for your open source apps or for some other proprietary thing that you also have on google play?
-
@failedLyndonLaRouchite@mas.to 2026-07-18 13:39
@daniel@gultsch.social for 30 years now the open source community has failed to learn the lesson that if you are open source, then the evil actors will just steal your stuff beyond that, very interesting in how over the last month, the daily flood of anti AI posts here has gone from "it doesn't even work" to "it is evil" cause anti AI people have realized that AI does in fact "work" in the sense of often being a very powerful tool took the anti AI people long enough
-
@tuban_muzuru@beige.party 2026-07-18 23:07
@daniel@gultsch.social Google doesn't solicit source code this way. There's no public "content offer pilot" program where Google Play buys developer codebases for training data — nothing matches this in Google's actual developer relations channels. Vague authority claim: "reaching out on behalf of the Google Partnerships team" is the kind of soft framing scammers use instead of a verifiable sender domain or named contact. The ask is the real payload: get you to submit your repos (including "archives of prototypes") through a portal you don't control, in exchange for a vague future "fee you propose." That's a plausible vector for source code theft, or at minimum harvesting IP/credentials via a fake portal. Urgency/exclusivity framing ("select group," "confidential pilot," "early adopter") is classic social-engineering pressure.
-
@womble@infosec.exchange 2026-07-19 02:50
@daniel@gultsch.social what they're willing to pay for proprietary codebases will be useful information for litigation on the copyright infringements against the open source codebases they trained on.