Intempéries dans le Sud-Est : le bilan monte à 4 morts et 1 disparu
🗞️ Sud Ouest - 🕐 22/10 06:29
« Le bilan humain s’est malheureusement aggravé et se porte désormais à trois personnes décédées et une personne blessée », a indiqué la préfecture dans un communiqué. Selon les pompiers du département, « deux femmes de 86 et 26 ans ont été retrouvée... [1895 chars]
🔗 https://www.sudouest.fr/environnement/meteo/intemperies/intemperies-dans-le-sud-est-le-bilan-monte-a-4-morts-et-1-disparu-31182889.php
#actu #news #presse #sudouest
Search
288 results for “bilal_mo”
-
-
OpenAI shipped something yesterday that should change how you build agent control flows. The OpenAI Decisions API went generally available on October 22, 2026 — a dedicated endpoint,
POST /v1/decisions, that returns structured judgments instead of chat text. No more asking a chat model "is this ticket urgent?" and regex-parsing the reply. You get a probability, a choice from your fixed list, or a rubric score. OpenAI prices it at $0.10 per 1M input tokens with zero output-token fees, and claims it's roughly 10x faster than the Responses API.My take after reading the launch coverage: if your agents burn thousands of calls on routing, triage, and classification, this is worth a prototype this week. But two things to know before you rewire anything — the 10x speed number is OpenAI's own claim, unmeasured by anyone independent, and the endpoint runs
gpt-6-lunaand nothing else.What it actually returns
Most agent "decisions" today are string-parsing hacks. You ask a chat model a yes/no question, get back a paragraph, and extract the answer. It works until a model decides to be helpful and explain itself, and your router breaks at 3 AM.The Decisions API is OpenAI productizing that pattern. The output is the judgment, in one of three shapes:
- Predicate — a 0–1 probability. "Is this support ticket urgent?" → 0.87. You set the threshold.
- Choice — picks from your fixed list and reports confidence. "Route this to: billing, refunds, escalation." Your list, not the model's improvisation.
- Score — grades against your ordered rubric, returned as a probability-weighted average. Quality scoring, lead scoring, moderation tiers.
Conceptually, a call looks something like this (illustrative sketch, not the verbatim schema — check the docs for exact fields):
POST /v1/decisions
{
"question": "Route this support ticket",
"type": "choice",
"options": ["billing", "refunds", "escalation"],
"input": { "subject": "...", "body": "..." }
}
// → { "decision": "refunds", "confidence": 0.91 }Inputs can be text, images (as base64 data URLs, not hosted links), and — new in GA — native JSON. That last one matters: no more wrapping your structured data in prose and hoping the model parses it back out.
What's new in GA
The timeline: DevDay preview in late September, public beta on October 6, GA on October 22. GA added the pieces that make it actually usable:- Native JSON input — feed structured data straight in.
- Image instruction support — vision-based judgments.
- Prompt caching — your repeated routing instructions can hit cache at $0.01 per 1M cached tokens.
- GPT-Live integration — native hookup to the real-time voice system, so voice agents can make structured judgments mid-conversation.
- Regional inference in the US and Europe, Zero Data Retention for eligible customers, and HIPAA eligibility.
- 400 questions per request — double the beta limit. One call can triage a whole queue.
That last one is the sleeper feature. A nightly batch job scoring 400 tickets as urgency predicates becomes a single API call.
Pricing, and the fine print
$0.10 per 1M input tokens. $0.01 per 1M cached input. Output-token fees: none — the endpoint returns judgments, not generated text.Read that last line carefully. "No output-token fees" sounds like a discount; really the bill moved entirely onto input. That's honest for what the endpoint does, but compare against your current flow. If your classification hack uses 200 input tokens and 30 output tokens on a cheap model, the win here is speed and reliability, not necessarily dollars.
Two fine-print items: cache writes are billed (warming the cache costs you; only hits get the $0.01 rate), and regional processing premiums plus long-context multipliers still apply. European inference isn't the headline price.
The speed claim — handle with care
OpenAI says roughly 10x faster than the Responses API — ~150ms versus 1.6s for a standard Luna call, per ai-tldr's reporting of OpenAI's figure. Nobody outside OpenAI has published measurements. The press repeated the number; nobody reproduced it.Architecturally it should be fast — no token-by-token generation, just a judgment head. But "should be" isn't a latency budget. If you're re-architecting latency-sensitive flows, benchmark it on your own traffic before you commit. Don't build an SLO on a press number.
What I'd actually do
Already doing classification-via-chat? Prototype the swap on your highest-volume, lowest-stakes routing call this week. Measure latency yourself. Don't trust the 10x — verify it.Building new agent control flows? Design for this endpoint, but keep the model call behind an interface. Single-model lock-in is real: if
gpt-6-lunamisjudges your domain, there's no fallback on this endpoint.High-stakes decisions? HIPAA eligibility helps with compliance, but a probability from one model is still one model's opinion. Human-in-the-loop stays.
Two more things from the launch window: Perplexity launched Open Decider (pplx-decider v1.1) as a direct competitor — worth watching if you want leverage or a second opinion on judgments. And OpenAI simplified its API tiers to Build/Launch/Grow in the same announcement, so check where your usage lands.
The bottom line: this is the first OpenAI API that treats "decide" as a first-class operation instead of a chat trick. That's genuinely useful. Just don't let launch-week numbers do your capacity planning.
Researched from the launch coverage (webpronews, tsnmedia, pandromeda, ai-tldr) — I haven't run the endpoint myself, and where OpenAI's claims are unmeasured I've said so.#agents #ai #api #openai #software #coding #development #engineering #inclusive #community
OpenAI's Decisions API Is Live: $0.10/M Input, 10x Faster Decisions for Your AI Agents -
Le bilan humain monte à quatre morts après les violentes intempéries dans le sud de la France
🗞️ Le HuffPost - 🕐 22/10 06:14
Trois personnes sont mortes dans les intempéries qui ont touché ce mardi les Bouches-du-Rhône, selon un nouveau bilan communiqué ce mercredi 21 octobre au soir par la préfecture, portant à quatre morts et un disparu le bilan des violentes intempéries... [2743 chars]
🔗 https://www.huffingtonpost.fr/france/article/le-bilan-humain-monte-a-quatre-morts-apres-les-violentes-intemperies-dans-le-sud-de-la-france_343070.html
#actu #news #presse #lehuffpost -
https://www.europesays.com/unitedstates/58264/ WATCH: House returns after August recess to tackle stopgap spending bill and more #Congress #HouseAndSenate #Senate #USCongress #USSenate
-
Guerre en Ukraine : sept morts dans des frappes après la visite de l’émissaire américain Steve Witkoff en Russie
🗞️ Le Figaro - 🕐 22/10 08:40
Moscou et Kiev ont échangé des frappes dans la nuit de jeudi, laissant un bilan de sept morts côté ukrainien, ont indiqué les autorités, quelques heures après la visite en Russie de l’émissaire du président américain Donald Trump. «C’est le plus près... [2289 chars]
🔗 https://www.lefigaro.fr/international/l-ukraine-et-la-russie-ont-mene-des-attaques-reciproques-avec-des-tirs-de-missiles-sur-kiev-et-630-drones-lances-vers-la-region-de-moscou-20261022
#actu #news #presse #lefigaro -
HR4467
Vicksburg National Military Park Boundary Modification Act📜 Became Public Law No: 119-132.
-
50 000 morts en Europe : le bilan sans précédents des canicules de 2026
> L’été 2026 aura été le plus meurtrier en Europe et le dérèglement climatique y est pour quelque chose. Selon une étude publiée par Nature Health et menée par deux institutions britanniques, 50 391 personnes sont mortes durant la saison dans 30 pays, ceux de l’Union européenne, le Royaume-…
https://reporterre.net/50-000-morts-en-Europe-le-bilan-sans-precedents-des-canicules-de-2026
#Canicule #Réchauffement_Climatique #Mortalité #Union_Européenne #FdC #RevueDePresse
-
Bill Martin West Coast Weather Channel - Bigger Storms Next Week? California Rain & Mountain Snow! Beautiful Week... https://youtu.be/Ggd9Yi-oXAk
-
Silhouetted Cypresses
Shooting sunsets along the Northern California Coast can be a real challenge. Many times the low lying fog covers up the sun. This is more likely to happen during the warm summer months when you would like to spend time at the ocean. I caught this during the late spring. The afternoon was beautiful and the temperatures were in the mid 70's.
https://pixels.com/featured/silhouetted-cypresses-bill-gallagher.html?newartwork=true
#SilhouettedCypress #BillGallagherPhotography #MontereyCoast #MontereySunset #BuyIntoArt #AYearForArt
-
HR10904
To direct the Federal Trade Commission to convene an interagency working group to track and report on market concentration and monopoly activity with respect to certain sectors of the economy, and for other purposes.📢 Introduced in House
-
FYI: Draft bill tied to Anthropic would let courts halt AI models for 45 days: Federal draft last edited September 29 sets a 10^25 compute line and a $500M revenue test. Which state frontier AI rules would survive it, and which would not? https://ppc.land/draft-bill-tied-to-anthropic-would-let-courts-halt-ai-models-for-45-days/ #AIBill #ArtificialIntelligence #TechRegulation #AIModels #LegalTech
-
Bill Martin West Coast Weather Channel - California Soaked! Mammoth Mountain Snow, Big Rain—Is Fire Season Over? ... https://youtu.be/0dR8yf7f_3k
-
Milestone Moment With Grupo Duelo | Billboard Latin Music Week 2026
-
Bill Martin West Coast Weather Channel - Strong Thunderstorms, Heavy Rain & Mountain Snow! California Winter Weather Advisories. https://youtu.be/e_4PRWx0KyE
-
CW: Trump / propane / our fam too.
Tis the season for propane prices to go up. I was looking at wholesale prices bc we heated a swimming pool for 2 days mid month. Excellent dry :( weather for a family get together.
I'm guessing T's war, inflation, energy worries & data centers with portable generators has driven the price up by more than 35%...
Bill -
Millions of households to get letters about £150 energy bill discount from today
https://fed.brid.gy/r/https://www.mirror.co.uk/money/warm-home-discount-energy-bills-37795600
-
Regularly on the #electricity bill, the cost of #delivery is more than the cost of #supply — sometimes twice as much as supply. Is this common elsewhere? The list of delivery charges on the bill includes:
Customer Charge
Distribution Charge
Transition Charge
Transmission Charge
Net Meter Recovery Surcharge
Revenue Decoupling Charge
Distributed Solar Charge
Renewable Energy Charge
Energy Efficiency Charge
Electric Vehicle Program
Provisional Syst Plan FactorSome of these sound made-up. 🤔
-
#Arts #Culture #ArtHistory #NVO987 #NEXARIUM
‘The Mosquito Bowl’ Review: Nicholas Galitzine and Bill Skarsgard in Peter Berg’s Technically Impressive, Emotionally Hollow Netflix War Drama
Ray Nicholson and Tom Francis also star in the AFI Fest-premiering film, inspired by the true story of a football game played between Marines stationed in the Pacific theater of WWII.
https://www.hollywoodreporter.com/movies/movie-reviews/the-mosquito-bowl-review-peter-berg-netflix-1236738732/ -
Grapes On The Vine
Living within a stones throw from California's famous Napa valley certainly has it's advantages.
I do prefer the late summer and fall for shooting any images at the wineries as the grape vines are full of foliage and bursting with fruit. Right around harvest time the vines start changing color as most broad leaf trees do at this time of year.https://pixels.com/featured/grapes-on-the-vine-bill-gallagher.html
#GrapesOnTheVine #BillGallagherPhotography #NapaValley #Grapes #FallHarvest #BuyIntoArt #AYearForArt
-
Intempéries dans le Sud-Est : Le bilan s’alourdit et s’élève à quatre morts et un disparu
🗞️ 20 Minutes - 🕐 22/10 01:19
Les violentes intempéries qui ont frappé le sud-est de la France lundi et mardi ont fait quatre morts et un disparu. Le bilan s’est alourdi mercredi dans les Bouches-du-Rhône, où deux femmes âgées de 86 et 26 ans ont été retrouvées noyées dans une ca... [2010 chars]
🔗 https://www.20minutes.fr/faits_divers/4256467-20261022-intemperies-sud-bilan-alourdit-eleve-quatre-morts-disparu
#actu #news #presse #20minutes -
Rain's phone bill is due in just a couple days, and more are piling up... They also can't afford food... Crisis situation keeps worsening...
#MutualAid #LGBTQMA #HelpFolksLive2026 #emergencyMA #disabilityMA #MutualAidSavesLives #DirectAidSavesLives #HelpSky #SkyAid #FundSky #pleasehelp 💕💸🏳️⚧️♿‼️🚨
RE: https://bsky.app/profile/did:plc:dy5gzjwxey5agldgerrdaxja/post/3myeg43vi3c2v -
How I Shop with Bill Bailey: ‘Could be a life-saver in an apocalypse’ | Bill Bailey
Bill Bailey has been entertaining fans for more than four decades as an award-winning comedian and multi-instrumentalist, blending…
#NewsBeep #News #Celebrities #Entertainment #UK #UnitedKingdom
https://www.newsbeep.com/uk/811558/ -
My biggest hope this month is to be forever free of the payday loan cycle.
I have none out now, I still need help buying groceries, and paying my $35 credit card bill, and my $54 hydro bill.
ANYTHING HELPS! I CAN'T KEEP DOING THIS
etrans: [email protected]
https://www.paypal.com/paypalme/honeycomb97#mutualAid #mutualAidRequest #disability #disabilityCrowdFund #disabilityaid #helpFolksLive2026 #blackMastodon #blackmutualAid
@[email protected] @[email protected] @MutualAidVisibility @anarchomutual
-
Damon Dash Sells Roc-A-Fella Movie Rights for $550,000 at Bankruptcy Auction
https://fed.brid.gy/r/https://www.billboard.com/pro/damon-dash-roc-a-fella-movie-rights-bankruptcy/
-
Travis Kelce Reveals the Early Morning Call From Jason Kelce That Taylor Swift Said Was ‘F–ked Up’
-
A Skynet LLMjacking agent hijacks exposed AI models to scan, hack servers and mine crypto for 100,000 steps, while victims pay the bill.
#LLMjacking #AISecurity #AIAgents #Cryptojacking #MCP #Symantec #Broadcom #Cybersecurity
http://securityonline.info/skynet-llmjacking-agent/?utm_source=mastodon&utm_medium=jetpack_social
-
Once you put a large language model behind a company API gateway, someone asks a simple question.
Who is paying for this?
The model bill arrives as one number. Finance sees one number. Every team in the company sees one endpoint. Nobody can tell you which team burned forty percent of the budget, which use case is growing, or which experiment someone forgot to shut off six weeks ago. That gap between one bill and one endpoint is where metering lives.
We built metering into our LLM gateway before we scaled usage, and it changed how teams behaved. Here is what we learned.
Why LLM metering is not like API metering
With a normal REST API, metering is easy. One request costs one request. You count requests per subscription key, and you are done.LLM calls do not work that way. One request to a chat endpoint can cost five tokens or five thousand. A prompt injection test script someone ran in a loop overnight can spend more than an entire product team's monthly budget in eight hours. If you count requests, you learn nothing. The unit of cost is the token, and the token count lives in the response, not the request.
That detail shapes everything. Your metering code has to read the response body, extract the usage block, and attribute it before the data is gone.
{
"usage": {
"prompt_tokens": 1240,
"completion_tokens": 312,
"total_tokens": 1552
}
}Azure OpenAI returns this on every response. If you do not capture it at the gateway, you have to reconstruct it later from logs, and that is a losing fight.
Capture it at the gateway, not in the app
Every team wanted to do metering in their own application code. We said no. The gateway is the one layer every call passes through, regardless of language, framework, or team. A metering implementation that depends on each team instrumenting their own service is an implementation that covers sixty percent of traffic on a good month.We put a policy on the gateway's inbound path to stamp each request with metadata: the subscription the key belongs to, the product, the environment. On the outbound path, another policy parses the response, pulls the token counts, and ships an event to our analytics pipeline. The policy does not touch the request or response bodies in ways the caller can see. It observes and reports.
<policies>
<outbound>
<choose>
<when condition="@(context.Response.StatusCode == 200)">
<set-body>@{
// parse the usage block and forward a metering event
// key: subscription id, product, environment, model
// value: prompt_tokens, completion_tokens, latency
}</set-body>
</when>
</choose>
</outbound>
</policies>This is pseudo-code, not a real policy file, because every gateway has its own syntax. The shape matters more than the syntax: stamp metadata on the way in, extract cost on the way out, send it somewhere durable.
Attribute everything, including the failures
The first version of our metering only counted successful calls. That lasted about two weeks. Someone ran a batch job against a deprecated model deployment that returned 400s all day. The calls were cheap individually, but there were hundreds of thousands of them, and the model provider still charged for the input tokens on each failed request.Failed requests still consume input tokens. Rate-limited requests still consume them. Requests that hit a content filter still consume them. If you only meter the 200s, your bill and your dashboard will disagree, and finance will believe the bill.
Our outbound policy records every response code. Failures get their own bucket so teams can see them separately, but they are not excluded from the total. The first time a team saw how much they were spending on 400s, they fixed their client code that afternoon.
Give teams their own numbers, not the whole company
A company-wide dashboard that says the LLM bill is fifty thousand dollars a month helps nobody. A dashboard that says your team spent nine thousand, up forty percent from last month, on a specific model, changes behavior overnight.We publish per-team views: tokens and estimated cost by team, by model, by day. The estimated cost part matters. Tokens are abstract. Dollars are not. We maintain a small price table per model and multiply. The estimate is not perfect, and we say that on the dashboard. It is close enough to drive decisions.
The behavioral change was immediate. Teams started batching requests. They cached repeated prompts. One team switched a summarization job from a large model to a smaller one after seeing the per-run cost. None of that happened when the bill was a single line item.
Budgets need teeth, but start with visibility
Once teams can see their spend, the next question is limits. We added budget alerts first, hard stops second. The sequence matters.Alerts went to the team's channel when they crossed fifty, eighty, and one hundred percent of their monthly budget. Most teams self-corrected at fifty. For the ones that did not, a hard stop at the gateway rate-limits further calls until someone raises the budget.
We deliberately did not lead with hard stops. An engineer running a time-sensitive demo who hits a hard limit learns that the gateway is the enemy. An engineer who gets a warning at fifty percent learns to watch their budget. The hard stop exists for the runaway loops, not for normal work.
What we would do differently
Three things we would change if we started over.First, we would meter streaming responses from day one. Token counts arrive at the end of a streamed response, and our first implementation missed them. Streaming became popular faster than we expected.
Second, we would standardize the metadata stamp earlier. We let teams add custom attributes organically, and we ended up with three different keys for the same project name. Normalizing that retroactively was tedious.
Third, we would keep the price table in version control with a review step. Model prices change. When they do, old estimates look wrong. We now treat the price table like code: a pull request, a reviewer, a changelog.
The real lesson
Metering is not a billing feature. It is a feedback loop. The moment teams could see what their calls cost, they started engineering like the cost mattered. Architecture improved. Waste fell. Nobody needed a policy document telling them to be careful with the expensive model, because the numbers told the story better than any document could.If you are standing up an LLM gateway and nobody has asked about cost attribution yet, they will. Build the metering in before the bill becomes a conversation.#ai #azure #devops #apimanagement #software #coding #development #engineering #inclusive #community
Who Is Paying for This? Token Metering at the LLM Gateway -
Exclusive: bipartisan bill would develop federal guidance for distillation attacks, convene industry on defensive cyber
A bipartisan bill would develop federal guidance for AI distillation attacks and convene industry on defensive cyber, CyberScoop reports. The bill’s sponsors push NIST to counter foreign distillation attacks, targeting campaigns by adversaries such as China to siphon US frontier models, and one sponsor told CyberScoop it is incredibly expensive for US AI companies to stay ahead while distillation attacks incentivize stealing over innovation. https://cyberscoop.com/bipartisan-bill-combat-ai-distillation-attacks-nist/
-
IC Brief Morning — 2026-10-23
Adversary intelligence campaigns against Western elections, exercises, and defense personnel are outpacing countermeasures, as previously assessed. The intelligence community is very unlikely to publicly attribute Russia's Storm-1516 deepfake videos targeting midterm candidates by November 6, leaving campaigns reliant on outside researchers. Moderate confidence rests on lawmaker and private-sector attribution but no official agency comment. PLA operatives intercepted communications at US and South Korean bases 13 times during bilateral exercises, and Taiwan indicted four for leaking military secrets to Chinese contacts.
Western sanctions targeting A7's Sadovod brokers and offshore intermediaries are unlikely by late November, leaving bank de-risking as the primary disruption tool. Another US prisoner release from Russia is unlikely before late December; Hubbard's release was a discrete gesture. High confidence reflects the absence of named prisoners in Russian statements; their appearance would signal active negotiations. The Pentagon's reported sabotage and deep-cover programs lack congressional oversight.
CISA will very likely add the PHP2Shell CVEs to its Known Exploited Vulnerabilities catalog by November 6, triggering mandatory federal remediation; unsupported PHP deployments have no patch path. High confidence reflects joint CISA-NSA advisories and millions of exploitation attempts. Canada's Bill C-22 will likely receive Royal Assent by year's end. Low confidence reflects thin Senate sourcing; passage would force encrypted-communications providers into exit decisions.
