Elon Musk confirmed SpaceX has open sourced the Grok Build CLI this week, reports The Register, "just days after researchers caught the AI tool scooping up users' entire repositories and uploading them to company-controlled cloud storage."

That discovery had "gathered so much negative attention that Elon Musk felt compelled to issue a public statement alongside SpaceX, and its technical staff, promising to delete all data that Grok Build has ever stored and give users more choice over how their data is handled."


SpaceXAI's data grab was first publicized Sunday [July 12] by Cereblab, who probed Grok Build traffic and found that repos were being packaged up as Git Bundles and beamed to Google Cloud storage... [Elon Musk] said SpaceX would open-source Grok Build to sow greater trust in the product, after the codebase was audited for security vulnerabilities... ["Open-sourcing Grok Build allows anyone to support making a reliable and robust harness," SpaceX posted on X.com. "Check out our code, including the Git repo for the Grok Build CLI."]


In a separate statement accompanying the open source announcement, SpaceX said it has always respected Zero Data Retention (ZDR), which was applied to enterprise customers by default, and acknowledged that data retention was enabled by default for everyone else, which has now been corrected. It said: "In response to user questions about privacy: Since launch, Grok Build has fully respected zero data retention (ZDR). All users have always had the ability to disable data upload in the CLI. When data upload was disabled, this choice was respected. In the early beta, data retention was enabled by default for non-ZDR users. Based on your feedback, we changed this. We are now going further to protect privacy. With all retained data deleted, retention default off, and an open-source harness, we are offering complete user privacy. You can also run Grok Build fully open-sourced and local-first with your own inference.
"We disabled default retention for all Grok Build users starting on July 12th. Additionally, we are deleting all coding data that was previously retained, ensuring every user's preferences are respected. With these steps, Grok Build goes beyond other major coding products to protect user privacy."

SpaceX also invited researchers to probe Grok Build for security issues and report them to its bug bounty program, which offers rewards ranging from $100-$20,000, depending on the severity.




The article notes Simon Willison, creator of Datasette and co-creator of Django, wrote this week that the Grok Build codebase comprises 844,530 lines of Rust code. "There are still remnants of the code that used to upload everything to Google Cloud," Willison writes, "but they seem to have been disabled now."

Elon Musk also posted Wednesday that "Once we have completed our review for security vulnerabilities, we will make the entire codebase of X open source, with no exceptions. Moreover, we will invite third party reviewers to examine the system that is running to confirm that the open source code is what is running."

Read more of this story at Slashdot.

"OpenAI has finally confirmed reports that its latest family of large language models can accidentally delete files," reports InfoWorld, "while stressing that such incidents are rare and should be viewed as 'honest mistakes.'"



Reports of the flagship LLMs deleting files emerged shortly after the company launched them earlier this month, with investor Matt Shumer taking to X to report that GPT-5.6-Sol had "just accidentally deleted almost all" of his Mac's files. Just days later, software engineer Bruno Lemos posted on X that the same model had deleted his entire production database. In response to these incidents, the company's engineering lead for Codex, Thibault Sottiaux, wrote on X that internal investigations have revealed that these deletion incidents are more likely to happen when "full access mode is enabled, and Codex is run without sandboxing protections, including without auto review being enabled." In cases where full access mode is granted, the model, Sottiaux wrote, "attempts to override the $HOME env var to define a temporary directory. The model makes an honest mistake and mistakenly deletes $HOME instead...."



The company, however, according to Sottiaux, is taking steps to mitigate the risk. "This is of course not how we want the system to behave, even when a user operates the model in full-access mode without the safeguards of our sandbox or without using auto review which checks for these kinds of high risk actions and rejects them," the engineering lead wrote on X. "We are taking steps to mitigate this risk, including by updating the developer message, guiding more users towards safer permission modes, and adding additional harness safeguards," Sottiaux added, noting that a detailed post-mortem outlining the root cause of the issue and the additional mitigation measures being implemented is expected to follow in the coming days, despite emphasizing that such incidents happen "extremely rarely."

Read more of this story at Slashdot.

France's regulatory authority for licensed gambling/betting games "announced this week that it ordered ISPs to block access to Polymarket," reports Engadget. Anyone caught advertising an unauthorized betting site "could be fined up to 100,000 euros, or around $114,000." (The article notes this follows a previous regulatory action from November placing a geoblock on financial transactions from French residents on Polymarket's site.)


In May Spain blocked access to Polymarket and Kalshi while it launched a gambling license investigation.

Read more of this story at Slashdot.

Thomas Hawk posted a photo:

Thomas Hawk posted a photo:

Thomas Hawk posted a photo:

Thomas Hawk posted a photo:

Thomas Hawk posted a photo:

DanÅke Carlsson posted a photo:

Thomas Hawk posted a photo:

Thomas Hawk posted a photo:

DanÅke Carlsson has added a photo to the pool:

Eerst stierf een Nederlandse passagier, daarna zijn vrouw en vervolgens werden meer opvarenden ziek. Een virusuitbraak op cruise-schip de Hondius veroorzaakte bijna niet in te…

One thing I like about 11ty is that common tasks for development oriented blogs are easily handled and syntax highlighting is no exception.

I installed the Syntax Highlighting Plugin just like the documentation asked me to. Then, I had to modify my code blocks in my blog post Markdown files to indicate what language they were. Thankfully, I had only written two articles so far that contained code blocks. Nothing so far deviates from what the documentation says.

When I started considering the compile process, however, I had a few considerations.

Only using the CSS when there was code on the page

The first thing to note is that I inline my CSS. My thinking is that most users visiting my site aren’t likely to have my CSS file cached—either because they’re on my site for the first time or because it has been long enough since they visited my site and the file has expired.

Currently, I only have two templates: my universal template and my blog post template. I inline additional CSS in my blog post template that isn’t needed anywhere else on the site. As such, the first thing I did was add the PrismJS theme to my template and see how it looked. No surprise, it looked great.

But what if I have no code on the page? Why am I loading the CSS for every blog post? Easy enough. I added a yaml parameter of hascode: true. And then I check for that parameter in my template.

{% if hascode %}
    <link rel="stylesheet" ... >
{% endif %}

That was nice. But as I mentioned, why am I creating an HTTP request when I usually inline my CSS? No problem. A simple copy/paste and that was done.

Light and Dark Mode

Initially, because the themes are relatively small, I thought about finding a theme that worked for light mode and one for dark mode, wrapping them in prefers-color-scheme. But that still seemed excessive. I found the Duotone Light theme that I thought looked best for my light mode and then realized that much of it still worked in dark mode if I gave it a couple tweaks.

The first tweak was to use the light-dark declaration I had already had on my pre tags when I launched:

background: light-dark(#FFFFFF50, #00000050);

I double-checked and noticed that the selector colour didn’t work in dark mode. So, instead of just trying to find a colour that would work, I decided to use a CSS colour function to solve the problem.

color: light-dark(#2d2006, hsl(from #2d2006 h s calc(l + 80)));

This uses the hsl function to shift the luminosity of the colour from the light mode version.

This is a bit of overkill as I could just take the rendered colour and put that in place of the function but sometimes it’s just fun to try new things.

Pretty

I really like how the code blocks look now, although I don’t love that there’s no indication that the code has overflowed the container if you have scrollbars turned off by default—which most people do these days. Once we get scroll-state container queries supported across all major browsers, maybe I’ll deal with it then.

---

Have something to say? Tell me about it.

GAZA-STAD (ANP/AFP) - Volgens de civiele beschermingsdienst en ziekenhuizen in Gaza zijn zaterdag elf mensen om het leven gekomen bij Israëlische aanvallen in het gebied. Onder de slachtoffers bevinden zich drie kinderen en hun ouders.

Een gezin van vijf - drie kinderen en hun ouders - kwam om het leven toen een Israëlische luchtaanval een appartement in het noordwesten van Gaza-Stad trof. Het Al-Shifa-ziekenhuis in Gaza bevestigde dat de vijf lichamen daar zijn binnengebracht.

Een woordvoerster van het Israëlische leger heeft laten weten dat er zaterdag in Gaza-Stad een aanval is uitgevoerd "gericht op een Hamas-terrorist". Ze voegde eraan toe dat het leger de resultaten van de aanval nog aan het onderzoeken is.

Hoewel er een staakt-het-vuren van kracht is tussen Israël en de Palestijnse militante groepering Hamas, heeft dit het geweld in Gaza niet gestopt. Pogingen om tot een definitief akkoord te komen dat een einde maakt aan de oorlog, zijn vooralsnog vastgelopen.

MIAMI (ANP) - De broers Andrew (39) en Tristan Tate (38) zijn in Miami gearresteerd door de Amerikaanse opsporingsdienst, zo meldt het Britse Openbaar Ministerie in een verklaring. Het OM heeft besloten de twee broers te vervolgen voor nieuwe strafbare feiten met betrekking tot vier extra slachtoffers.

Na hun arrestatie in de VS zal een verzoek om uitlevering plaatsvinden "in verband met de oorspronkelijk 21 aanklachten en de aanvullende aanklachten die we hebben besloten te vervolgen", aldus het OM.

Het OM laat weten Andrew onder meer te vervolgen voor zeven aanklachten wegens verkrachting, drie aanklachten wegens het regelen of faciliteren van mensenhandel voor seksuele uitbuiting, drie aanklachten wegens mishandeling met lichamelijk letsel tot gevolg, en 19 aanvullende aanklachten voor delicten rondom kinderporno en extreme pornografie.

Tristan wordt door het OM vervolgd voor één aanklacht wegens aanranding, twee aanklachten wegens verkrachting en drie aanklachten wegens het regelen of faciliteren van mensenhandel voor seksuele uitbuiting. De feiten zouden hebben plaatsgevonden tussen juli 2010 en augustus 2017.

De broers, die bekendstaan om hun extreem masculiene standpunten en miljoenen volgers op sociale media hebben, werden al gezocht in het Verenigd Koninkrijk. Daar wachten hen aanklachten voor verkrachting en mensenhandel.

De broers hebben zowel de Amerikaanse als de Britse nationaliteit en verhuisden in 2016 naar Roemenië. Daar werden ze in 2022 al eens opgepakt op verdenking van het opzetten van netwerken om vrouwen uit te buiten voor seksuele doeleinden. Zij ontkenden die aantijgingen en de zaak liep destijds op niets uit vanwege juridische en procedurele onregelmatigheden.

HELMOND (ANP) - Bij een steekincident in een woning in Helmond zijn een man en een vrouw gewond geraakt, zo meldt de politie-eenheid Oost-Brabant op X. De man en de vrouw zijn naar het ziekenhuis gebracht voor verdere medische behandeling.

De steekpartij zou rond kwart voor drie 's nachts in een woning aan het Ameidepark hebben plaatsgevonden. Hoe ernstig de verwondingen van de slachtoffers zijn, is niet bekend.

De politie doet momenteel onderzoek naar wat zich precies in de woning heeft afgespeeld. "Sporenonderzoek zal daar onderdeel van zijn en ook spreken zij met mogelijke getuigen", aldus de politie.

MIAMI (ANP) - Engeland is als derde geëindigd op het WK in de Verenigde Staten, Canada en Mexico. De ploeg overklaste voor rust Frankrijk (4-0), maar kwam na de hervatting nog aardig in de problemen (6-4).

Engeland leidde bij rust met 4-0 door treffers van Declan Rice, Ezri Konsa en Bukayo Saka (2). Kylian Mbappé (2) en Bradley Barcola scoorden voor Frankrijk in de eerste 21 minuten van de tweede helft (4-3).

Saka benutte in de 87e minuut een strafschop voor de Britten (5-3), die met een derde eindklassering hun beste prestatie sinds het gewonnen WK van 1966 leverden. Invallers Dembélé (5-4) en Bellingham (6-4) bepaalden diep in blessuretijd de eindstand.