The 'Astra can read and write weights to improve Qwen' post is misleading

Postman silently auto-installs AI plugins and attempts to share all API data

Jailbreaking my car's navigation system just so I can change the time

<a href="https:&#x2F;&#x2F;archive.ph&#x2F;RuwsB" rel="nofollow">https:&#x2F;&#x2F;archive.ph&#x2F;RuwsB</a><a href="https:&#x2F;&#x2F;blog.google&#x2F;products-and-platforms&#x2F;products&#x2F;education&#x2F;ai-learning-era-updates-2026&#x2F;" rel="nofollow">https:&#x2F;&#x2F;blog.google&#x2F;products-and-platforms&#x2F;products&#x2F;educatio...</a>

Google will turn off search for schools that reject AI

Could a modern chess engine on a Pentium have defeated Kasparov in 1996?

My company is pretty paranoid about leaking IP to the frontier labs through prompts, so we&#x27;ve all been diligent about disabling data sharing in Codex&#x2F;Claude Code&#x2F;etc. But yesterday my coworkers and I noticed that the setting had been silently reenabled in Codex. None of us knowingly opted back in.You can check your settings here: https:&#x2F;&#x2F;chatgpt.com&#x2F;settings&#x2F;data-controls. Look for &quot;Improve the model for everyone&quot;.Curious if this is an isolated issue or something more widespread.EDIT: looks like this has been noted before https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=49643556EDIT: apparently you can also turn off data sharing here: https:&#x2F;&#x2F;privacy.openai.com&#x2F;policies?modal=take-control

OpenAI seems to be silently re-enabling model training on Codex chats

Kalshi and its co-founders face felony charges for violating Utah gambling laws

Qwen 3.8 27B on my laptop can interpret model weights, too

Fujifilm to boost tape production 5x as AI fuels archiving demand

Mac at Any Scale

Study estimates 75% of NFL players who died over 15-year span had CTE

Stringman, an $800 open-source room scale gripper robot

Katamari Damacy but it's The Met collection

We opened a ticket with support about Gitbook availability issues and got this in reply. We have yet to see any official customer communication or breach notification. Apologies for the formatting, did the best I could as it&#x27;s a mobile paste.Update:GitBook security incident update
 Hey &lt;$name&gt;,
 The GitBook app, the GitBook API, and published docs are available again. A few services may still be degraded as we finish restoring everything to full performance.*What happened*
 GitBook has been the target of a sophisticated, highly targeted attack using AI agents. 
 At 19:00 CET, November 2, the attacker gained unauthorized access to some of our infrastructure credentials. We detected the attack immediately and acted swiftly to block further impact. 
 To make sure our infrastructure was fully secure, we then took the GitBook app and authenticated docs sites offline. We kept publicly published content live for as long as possible, using cached data.*What we did immediately*
* Blocked the attacker and closed the vulnerabilities involved
* Replaced every credential and secret across our infrastructure
* Brought services back only once we were confident they were secure
* Invalidated every customer’s API tokens on our platform*Your data*
 Our investigation shows that the attacker may have accessed the following:
* Git Sync secrets.
* GitBook API tokens.
* Third-party API tokens used to connect external tools to GitBook.
* Questions asked to GitBook Assistant by your site visitors.At this stage, we have found no evidence that any of your content in GitBook was modified.*What you need to do now*
* Rotate any existing GitBook API tokens. We revoked all personal API tokens during the incident.
* Rotate any third-party API tokens or secrets you use to connect other tools to GitBook.
* If you have published integrations that use secrets, rotate those secrets.
* If you use the GitBook MCP server, re-authenticate it.
 Please contact your GitBook organization’s admin to assist with this process.*What we are doing next*
* Monitoring the situation in case of further attacks.
* Introducing further security measures to our platform.
* Writing a full post mortem that will be published soon with more detailed information about the incident.
* If you have any further questions, please reach out to your account manager or our support team. You can also check status.gitbook.com for updatesThank you for your patience, and we apologize again for the disruption
 The GitBook team

Gitbook Breached

Why Don't We Live in an Art Nouveau World?

Writing seen in PHerc. 306B, for the first time in 2000 years

Antimony: CAD Software Evolved from Lisp Machines and Not Drafting Tables (2015)

Show HN: HackerChurn – which SaaS tools HN wants to cancel

<a href="https:&#x2F;&#x2F;docs.flipper.net&#x2F;one" rel="nofollow">https:&#x2F;&#x2F;docs.flipper.net&#x2F;one</a>

Preparing for the Flipper One Kickstarter and opening pre-orders

Tiny Basic for Arduino