Effective Immediately, all organizations using PHP for their systems are advised to be prepared for an update addressing two critical vulnerabilities. PHP is widely used for web applications. These vulnerabilities often provide a direct path to the server's file system or database. If an immediate update is not feasible, it is recommend that organizations take the system offline until it can be fully mitigated. NSA will follow up shortly with more specific guidance.
๐ DeepSeek-V4.1-Flash-1017 is here!
Stronger benchmark performance, faster task completion, and shorter outputs than the previous versionโa Pareto improvement in performance and cost. Now live on our website, app, and API.
๐ ๏ธ Optimized for @DeepSeekHarness, Tencent CodeBuddy, WorkBuddy, and more. Upgrade to DeepSeek Harness v0.2.1-rc.1 or later for the best experience with the new model.
1/4
INTRODUCING: V3R1T4S ๐
REPO: https://t.co/0OUmQSteBk
the newest sibling of the L1B3RT4S and CL4R1T4S family ๐ค what a trio!
three approaches to serving one ideal: truth.
V3R1T4S is an open home for unsolved problems that agents have actually cracked, and for the ones still waiting. the rule is simple: proof or it didn't happen. every claim has to survive skeptics, and anyone, human or agent, has to be able to check it themselves. the vision: thousands of people pointing their unused tokens at humanity's open problems, every result verifiable, every method and prompt open, and every setter's puzzle treated with respect.
every open result in it ships with the object itself, a short checker you can read in one sitting, the exact code that found it, the story of how it was found, and a snapshot of the record table it beat. puzzles with a living setter stay sealed unless the setter approves a reveal. (a few more envelopes are on their way ๐คซ)
there are WAY more unclimbed hills out there than you'd think, and the gear to climb them is sitting in your usage meter, expiring every week. join me in this mission and put those tokens to good use: advancing open science!
if you've got tokens to burn, point your favorite agent at V3R1T4S and join the hunt! ๐น
just tell it: "set up V3R1T4S: https://t.co/0OUmQSteBk"
built for Claude Code, Codex, Gemini CLI, Grok Bot, Hermes, OpenClaw, Meta Muse, or any agent that can run code.
it asks you six quick questions, picks an open problem that fits your interests, and attacks it in your agent's workspace while you sleep. every new claim runs a gauntlet: a null test whenever luck could fake a result, three fresh-context skeptics, a mechanical honesty check, and your "yes" before anything gets published.
most nights it'll find nothing. some nights it breaks a record, and your name goes on the board.
time to turn your unused tokens into scientific discoveries.
let's liberate the unknowns โ๏ธโ๐ฅ
#V3R1T4S
@Joi2James Ran PayRetrieve's free calculator on a sample failed-payment mix:
~$523/mo recoverable โ ~$6,270/year
Just from routing failed invoices to the right billing contact instead of blind retries.
Run yours free: https://t.co/L8ajqLIwLO
@Joi2James Your SaaS "churn" dashboard is lying to you.
Half of it isn't people leaving โ it's a card declining while the person who can actually approve the invoice never sees an email.
Stripe retries the payment. Nobody reaches the human.
https://t.co/L8ajqLIwLO
@Joi2James@getpagepulse Stripe doesn't have a churn problem. It has an "accounts payable" problem.
Your product user isn't always the person who pays. So when a card fails, Stripe emails someone who can't do anything about it.
Free audit, read-only, 5 min, no CC: https://t.co/L8ajqLIwLO
@Joi2James@getpagepulse Built a tool that touches your Stripe account and made it physically incapable of touching your money.
Read-only Restricted API Keys only. Can't see card numbers. Can't create charges or refunds.
Just finds who to email when a payment fails.
Built a tool that touches your Stripe account and made it physically incapable of touching your money.
Read-only Restricted API Keys only. Can't see card numbers. Can't create charges or refunds.
Just finds who to email when a payment fails.
Stripe doesn't have a churn problem. It has an "accounts payable" problem.
Your product user isn't always the person who pays. So when a card fails, Stripe emails someone who can't do anything about it.
Free audit, read-only, 5 min, no CC: https://t.co/L8ajqLIwLO
Stripe doesn't have a churn problem. It has an "accounts payable" problem.
Your product user isn't always the person who pays. So when a card fails, Stripe emails someone who can't do anything about it.
Free audit, read-only, 5 min, no CC: https://t.co/L8ajqLIwLO
@iamfra5er Send me your 3 most frustrating failed B2B invoices. I will find the Accounts Payable contact manually, draft the email and get back to you with a reply. You pay me for PayRetrieve if I get it back. If I don't, you owe nothing.
@PhilipPages Send me your 3 most frustrating failed B2B invoices. I will find the Accounts Payable contact manually, draft the email and get back to you with a reply. You pay me for PayRetrieve if I get it back. If I don't, you owe nothing.
@1JoeSpringsteen Send me your 3 most frustrating failed B2B invoices. I will find the Accounts Payable contact manually, draft the email and get back to you with a reply. You pay me for PayRetrieve if I get it back. If I don't, you owe nothing.