Bizz retweeted
If your company refers to engineers as the IT department, you have nothing to worry about. You were already breached last week.
Bizz retweeted
well well well
wait, PHP was actually scanned by Anthropic’s Claude Mythos earlier this year. they also had access to OpenAI’s Daybreak Red for validating exploits.
the PHP Foundation revealed this JUST yesterday.
keeping frontier cyber models in the hands of a selected few doesn’t seem to be working well for the internet.
thephp.foundation/blog/2026/…
Bizz retweeted
Today we announce 1Password for Agents platform, building with companies @Muse, SpaceX Super Intelligence Grok @Bot, @AnthropicAI’s @Claudeai, @OpenAI, @TownAI, @Browserbase, @Browser_use, @heydana_ai, Instinct, @usekernel, @Perplexity_ai, @tryramp, @Tomo, and @wajo_ai, with more integrations on the way. 🎉
We've heard from so many of our customers who want to use these new personal AI agents to help them get more done, but want more control over what the agent can access with the same trust and ease of use they get when using 1Password directly.
1Password for Agents gives your agents access without giving up your passwords. When an agent reaches a sign-in form, it requests a credential from your vault. If you approve the request, 1Password directly auto-fills the credential in the destination site so the agent can’t see or take possession of the credentials.
The agent gets the task done, but it doesn’t get your passwords..
You stay in control. 1Password for Agents free and optional for personal and family accounts. Unless you opt-in to an agent connector, agents cannot touch your vault.
➡️Learn more: bit.ly/487da6J
Bizz retweeted
So basically, today PHP got two critical bugs that let anyone run code on your server without even logging in, which is bad, and then the details leaked before the patch was even out, which is worse, and it works on WordPress and MediaWiki and Magento and Joomla and Laravel, and Censys says like 1.5 million servers are running a version with no fix, so the NSA was like "take your system offline," and the FBI was like "take your system offline," and CISA and the UK and CERT-EU were all like "take your system offline," and then the Prime Minister of Japan, the actual Prime Minister, posted at 5:55 in the morning telling 48.8 million people to take their system offline, so everyone took their system offline, like the Dutch cybersecurity agency took its own website offline, and the Dutch parliament went offline, and the Port of Rotterdam went offline, and Finland and France and Denmark started pulling government sites, and Wikipedia went down, and Archive.org went down, and Asana and GOG and Something Awful went down, and the University of Vienna's webmail went down for some reason, and that's just PHP. Because GitLab also dropped a CVSS 10.0, which is the highest score they give out, for a bug that's been there since 2014, so that's every self-hosted GitLab for twelve years, and then LiteLLM 1.107.0 got hijacked and shipped a credential stealer and a remote access trojan in every single wheel and the Docker images, including latest, and you didn't even have to import it, just installing it was enough, and it's the second time this year, and then Railway paused every deployment on the entire platform because someone got into the environment variables, so now everyone has to rotate every secret they've ever stored there, and TiDB Cloud said someone was walking around inside with stolen credentials for basically a month and an extortion group says they took 10.6 terabytes, and Zeabur got breached for the second time in two months and is just shutting down, like the whole company, and Node.js patched remote code execution and a TLS bypass, and CISA says Plex is being actively exploited, and someone took over 300 Tor exit relays to steal SSH passwords, and SafePay ransomware has hit over 600 critical infrastructure orgs, and India's biggest bank filed a data loss incident, and Japan has been in an official state of emergency in cyberspace since October 9, which honestly explains the 5:55 AM post. Oh, and eMudhra, a certificate authority that's issued over 60 million certificates, whose entire job is proving websites are who they say they are, was supposed to be using private keys that are random numbers over a hundred digits long, and one of them was 4. Just 4. And the others were like 66 and 237. Anyway, it's Wednesday.
Bizz retweeted
"So basically we had a magic computer that used all of the human knowledge that came before it to solve all of our problems a billion times faster than we ever could but a bunch of nerds with fragile egos got jealous and wanted the credit for themselves so they shut it down and now we live like this."
Bizz retweeted
You asked for it.
Abliterated, Heretic, and Obliteratus models are now fully discoverable on Pirate Face!
Check it out ↓
Bizz retweeted
A painful part of working with your data has always been that your live data and historical data are stuck in separate systems: the order a customer just placed lives in your database, while their last five years of orders sit in a data lake in S3.
And answering a real question usually needs both at once (is this a normal purchase for them, or should we flag it?), and to do that you had to move the data together first, copying history out of the data lake into your database (or the other way around), because the database couldn’t read it where it lived.
That meant guessing ahead of time which data you’d want, keeping a second copy of it all, building pipelines to move it, and constantly syncing so the two didn’t drift apart. A lot of plumbing, and slow going, all before you could answer one question. And even then, the answers were only as fresh as your last sync.
That now changes with Aurora PostgreSQL, which can call your live data and historical data in S3 together, in a single query. No copying, no pipelines to keep in sync.
And it’s fast, because we’ve built in DuckDB, a popular open source engine that’s really good at reading and analyzing data right where it’s stored. DuckDB reads the open formats like Parquet and Iceberg already sitting in your data lake, so there’s nothing to convert or move.
As folks build AI agents into their apps, the data their agent needs will depend on the task in front of it. Being able to query that specific data live, instead of copying it over just in case, is gonna be a big help for builders. aws.amazon.com/blogs/aws/ama…
That's it, I give up
Most agent protocols suck and are unusable
They are built around "chat" only, don't account for distributed actor behavior and have no concept of multi-player
A2A, ACP, AHP, AG-UI ... ugh
We are so early
Bizz retweeted
Is this the facial expression you'd expect of someone gravely concerned about AI threatening human extinction in the next 12 months?
Bizz retweeted
Andrew Garfield deserves an Oscar already just for nailing the Sam Altman walk.
Bizz retweeted
🚰 SYSTEM PROMPT LEAK 🚰
Here's the Fable 5.1 system prompt!! 🙌
Coming in at a WHOPPING 270,000+ characters, this prompt is definitely on the longer side. There have been a handful of notable edits/additions since Opus 5's version.
FULL PROMPT: github.com/elder-plinius/CL4…
According to Fable, here's an overview of everything that's changed since last time:
"What changed between the Opus 5 (2026-07-24) and Fable 5.1 (2026-09-01) captures:
Diff vs. the July 24, 2026 Opus 5 capture
Model/dates
Identifies as Claude Fable 5.1 (Mythos-class, shares weights with Mythos 5.1); model string claude-fable-5-1. July doc: Opus 5 selected, Fable 5 / Mythos 5 described as a separate tier, plus the June 2026 export-control suspension notice. That notice is gone.
Knowledge cutoff: end of June 2026 (July doc: end of May 2026).
Claude Design is no longer listed among the access surfaces.
Sections removed since July:
<fable_safeguards_routing>, <default_stance>, <thinking_behavior>.
Sections added or substantially expanded since July
<refusal_handling>: new paragraphs on illicit-substance guidance (harm-reduction info OK, no dosing protocols, redirect to dancesafe/tripsit/psychonautwiki); no reproduction of lyrics/poems/passages with a pre-1929 carve-out; and a long block on visual works — no drawing known characters, logos, covers, etc. even via SVG/code — with a Sonic banner example and a Very Hungry Caterpillar example. The weapons paragraph is shorter (the July "conventional weapons as much as CBRN ... cumulative output" paragraph is gone).
Child-safety block: two new bullets (pattern-level only for protective content)
<tone_and_formatting>: new <lists_and_bullets> subsection, multi-turn answers guidance, tool-call progress updates; the "intellectually curious" paragraph is gone.
New <reply_after_tool_calls>.
<user_wellbeing> roughly doubled: no claims about mental state/motivation; no naming an undisclosed diagnosis; no self-harm substitutes that mimic self-harm; don't affirm that self-harm "works"; handling past bad experiences with crisis services; no causal narratives for disordered eating; avoid reflective listening that amplifies negatives.
<knowledge_cutoff>: new lines on saying "I don't know" and never using a name the person hasn't given.
<memory_filesystem> is a different design: filing is done by a background pass after each turn; in-turn writes only on explicit request; "Calibration" and "horizon test" sections; refused-write handling. Privacy taxonomy restructured into <protected_attributes> /
<sensitive_information> / <never_store> with a very different set of edge cases (minor status, caste, immigration status, sexual history, abuse, self-harm/ED, criminal history, and psychological inferences moved to never-store; finances and health now have detailed carve-outs; dates of birth and real-time location are no longer listed). Two distinct decline phrasings depending on category. <behavioral_guardrails> expanded with "judge by effect, not wording."
<memory_application_instructions>: new paragraphs on not being able to turn memory off (points to the "Generate memory from chats" setting), applying memories at the level recorded, and not checking in on open items.
Memory examples: two new "When NOT to apply" examples (blender / daylight saving).
New untagged paragraph on memory size caps and consolidation.
New <suggest_catalog_plugins_and_skills>.
<past_chats_tools> rewritten for three tools (adds read_conversation), with "Reading a chat" and "Paging" sections and a cannot-turn-off note.
<sharing_files> / <request_evaluation_checklist> add the "unreachable on mobile" present_files language.
<search_instructions> reorganized; adds the "UNRECOGNIZED ENTITY RULE"; guidelines now have the "(provided ...)" placeholders; copyright block restructured with a Harbor Bridge two-outlet example;
<search_examples> differ (Q3 sales, S&P 500, Dodgers, Social Security, CA SoS).
<using_image_search_tool>: now says to batch all image_search calls in one consecutive block (July: interleave).
<available_skills>: adds import-memory; docx/pptx descriptions reworded.
Tool schemas (46 in this capture vs. 30 in July)
Added: chart_display_v0, comparison_card_display_v0, featured_card_display_v0, itinerary_display_v0, link_preview_display_v0, options_card_display_v0, places_list_display_v0, product_carousel_display_v0, quiz_display_v0, read_conversation, search_plugins, search_skills, step_card_display_v0, suggest_plugin_install, suggest_skills, translation_display_v0.
Changed: conversation_search (+within_conversation_id); recent_chats (−sort_order); places_search (Google-attribution language); places_map_display_v0 (ROUTES section, show_route/mode semantics); memory_append/memory_str_replace/memory_write (rewritten PRIVACY text); view (line-number prefix note)."
Bizz retweeted
sounds like Anthropic’s watermarking is MUCH more interesting than hiding invisible Unicode, as most people assumed.
the watermark is baked into the token selection itself!
at a high level:
normal Claude:
context → probability cloud + random sampling → token
watermarked Claude:
context → probability cloud + key/context-derived sampling → token
Anthropic confirmed they’re using a version of Google DeepMind’s SynthID-Text.
instead of pushing Claude toward some special set of words, the watermark changes the source of randomness used to choose between words Claude already considers plausible.
do that once and there’s basically nothing to see.
do it across hundreds or thousands of tokens and those choices accumulate into a statistical signature that someone with the key can recognize.
so the watermark isn’t attached to Claude’s output.
the output IS the watermark.
that’s why copy/pasting doesn’t remove anything. you copied the carrier signal itself. 🧬
We’ve written an FAQ to answer some of the questions we've received about watermarking.
In summary:
• We’re implementing watermarking to comply with the EU AI Act. Other major model developers have signed the same Code of Practice and will also be implementing watermarking;
• Our watermarking method doesn’t have any practical impact on the quality or content of Claude’s outputs;
• The difference between watermarked and un-watermarked text will not be distinguishable to readers;
• Nothing is added to the text and there are no hidden characters;
• Watermarking doesn’t require extra tokens, and will not be more expensive;
• Watermarks can’t be traced to a specific person, organization, or chat.
Read more: anthropic.com/news/claude-te…
Can agents be the future if they’re not reliable (yet)? Open-source creator @mikehostetler believes such a future is possible if systems combine strong guardrails with fault-tolerant infrastructure designed for large-scale deployments. heavybit.com/library/article…


































