The author said they had become aware of multiple attempts to exploit their permissive licensing to take control of their work. They questioned what people thought “permissive” meant, mentioning vibes, papers and essays.
The author wrote that they expected their organisation to be hacked repeatedly, with some attacks being sophisticated and others exposing it as incompetent. They said it would do its best to prevent the breaches but expected them to happen regardless.
The author wrote that they learned someone had died after receiving a bug report about the person’s obituary displaying incorrectly in a browser, and described the experience as difficult to put into words.
The author wrote that millions of people with no previous coding experience had started building their own apps this year, and predicted that millions more would do so in the coming years. They said they believed most new apps would be web apps, arguing that native apps involved too much friction for casual developers.
The author wrote that browser content renderers could never be made completely safe from malicious takeover. They said the main architectural priority should be to sandbox them aggressively and assume they were under hostile control.
The author wrote that understanding the future of open-source software required examining the XZ Utils backdoor attack. They asked readers to consider the potential value of such a vulnerability and the time and effort involved in putting it in place, then began a further hypothetical that ended mid-sentence.
It's irresponsible for any security-sensitive OSS project to accept public PRs. AI code review is amazing, but it doesn't solve this. Attackers can keep trying indefinitely under new identities. You have to catch every malicious contribution. They only have to get one through. #OpenSource #Security #CodeReview #Thetweetdoesnotmentionanyspecificcountries.Thus #theresponseis:
Once we put out the alpha version of @ladybirdbrowser, you're gonna see it get hacked and owned over and over. This is expected. It'll be a natural part of the development process as we spend the coming years transforming Ladybird from a proof-of-concept into an end-user #LadybirdBrowser #WebDevelopment #AlphaRelease #Nospecificcountrycodesarementionedinthetweet.
Over the coming years, more and more people will see parts of their expertise replicated by AI, and many of them are going to be extremely upset about it and shame you for thinking it's neat. The software profession is in the middle of this right now, and it's pretty ugly. It's #AI #SoftwareDevelopment #Automation #Therearenospecificcountrymentionsintheprovidedtweet.Therefore #theresultis:
You cannot defend software against AI-powered attackers without AI-powered defenders. Security-sensitive projects that do not embrace AI will find themselves drowning in exploits. #CyberSecurity #AI #DefendAgainstAI #Thetweetdoesnotmentionanyspecificcountries.Therefore #therearenocountrycodestoreturn.
The “Code of Conduct,” as it typically functioned over the past decade, was a naked emperor. Anyone awake could see that it enforced extreme progressive politics, but few dared say so because the professional and social consequences could be very real. Whenever a project #CodeOfConduct #ProgressivePolitics #StandUp #Nospecificcountrycodesarementionedinthetweet.
My guess: the big differentiator in modern software development will not be "taste", but sustained attention. Most software built quickly with AI will follow an "easy come, easy go" pattern and be abandoned shortly after announcement. #SoftwareDevelopment #AI #SustainedAttention #Nospecificcountrycodesarefoundinthetweet.
Another week, another "AI policy" focused on maintainer annoyances while ignoring the security elephant in the room: We're now in an age of near-zero-cost code generation. Malicious actors can flood a project with a thousand benign PRs to make one malicious change disappear into #AICode #SecurityThreats #OpenSource #Therearenospecificcountriesmentionedinthetweet.
Millions of businesses are running on load-bearing Excel sheets that take hours of manual maintenance every week. Insane global economic value waiting to be unlocked here. #Excel #Automation #BusinessEfficiency #Nospecificcountrycodesarementionedinthetweet.
We obsess about browser fingerprinting and cookies because it's something we can at least get a handle on. Meanwhile the really bad privacy abuses happen server-side, and there isn't a damn thing your browser can do about what happens to your data after you've handed it over. #Privacy #DataProtection #BrowserFingerprinting #Nospecificcountrycodesarepresentinthetweet.
Hobby programming is in a weird place right now, as projects that used to be hella impressive can be done in a couple hours with AI. But most AI hobby projects we see are pretty low-effort and thrown together quickly. I'm pumped to find out what happens as hobby hackers start #HobbyProgramming #AIProjects #CodingLife #Nocountrycodesfoundinthetweet.
Maybe it’s technically allowed, but it seems obviously wrong to accept donations under a name that strongly implies one purpose, then shuffle that money toward completely unrelated projects. I wonder how many donors know what they’re actually funding. #Transparency #Ethics #DonorAwareness #Nospecificcountrycodesarementionedinthetweet.
The key thing to understand about OSS going forward is that problem reports are now more valuable than code submissions. For security-sensitive projects, public PRs now have net negative value: cheap to produce, expensive to review, and risky to accept. #OpenSource #Security #CodeReviews #Nospecificcountriesarementionedinthetweet.Therefore #theresponseisempty.
If your security model hinges on humans reliably spotting AI-generated text or code, you don’t have a security model. #Cybersecurity #AI #SecurityAwareness #Nospecificcountrycodesareidentifiedinthetweet.
This is really sad. It kills something that made open source magical for so many of us, myself included. But the problem is real, and we need to deal with it as an industry. First step is opening our eyes to how much the economics have changed. #OpenSource #TechIndustry #Economics #Nospecificcountrycodesarementionedinthetweet.
Claim it. Contact us at [email protected]