iain.davidson100 has added a photo to the pool:

iain.davidson100 has added a photo to the pool:

iain.davidson100 has added a photo to the pool:

Google Cloud has admitted it made a configuration change that means some customers of its VMware Engine (GCVE) can’t use stretched cluster. A G-Cloud incident report time-stamped 13:24 PDT on July 14 (21:24 UTC) reports some customers “are experiencing zonal outages impacting network connectivity across multiple regions” and that the trouble started at 10:00 PDT. Google first attributed the problem to “an underlying network connectivity issue affecting the infrastructure that links the zones within a stretch cluster,” and warned “This disruption is causing synchronization issues between the affected zones.” Storage and compute services weren’t impacted, and VMs kept running. Users just couldn’t reach their virtual servers. That’s bad because the whole point of stretched clusters is to enhance resilience by creating a virtual pool of resources that spans two physical sites, while keeping the two rigs in synch to enable rapid failover without disruption. Google’s next update offered “underlying inter-zone communication failures and Border Gateway Protocol (BGP) session flapping between cluster zones” as the reason for the mess, adding “Specifically, network connectivity has been lost between the affected zones and the witness appliance. Because the witness appliance is currently unreachable, the cluster zones are unable to safely synchronize state.” At 16:05 PDT Google ‘fessed up. “Our investigation has identified a recent configuration update that is the likely cause of the inter-zone network disruption,” the web giant admitted. “Teams are working on remediation.” Google hasn’t said when it will set things right, so customers in the impacted regions – australia-southeast1, australia-southeast2, europe-west3, and northamerica-northeast2 – must wait to learn when they’ll once again enjoy the resilience they pay for. Other VMware customers may not want to wait because the Broadcom business unit on Tuesday warned of seven flaws in its VMware Avi Load Balancer. One of them, CVE-2026-47865, is an authentication bypass vulnerability that earned a CVSS score of 9.8. The product’s name is a little misleading, as it’s actually a full Application Delivery Controller that includes load balancing and a Web Application Firewall VMware hasn’t said much about the flaw other than warning “A malicious user with network access may be able to access the Avi Control plane by bypassing the authentication mechanism.” The tool works with VMware’s Cloud Foundation bundle, Kubernetes Service, and can connect resources in public clouds. Unauthorized access is therefore distinctly undesirable. The five remaining CVEs are also significant, with CVSS ratings ranging from 8.8 to 7.1. Broadcom has fixed the flaws in recent updates to the product. ®

OpenAI has never been as open as its name suggests and is becoming even less so. The free-spending AI giant recently revised the multi-agent orchestration in its Codex command line interface to encrypt messages passed to subagents. OpenAI's Codex supports multi-agent orchestration, a way to have a parent agent spawn child agents or delegate tasks to other agents that may call out to different models. Codex/GPT-5.6 introduced a protocol called multi-agent v2 that appears to be geared toward letting the runtime allocate work instead of leaving those decisions to user-declared configuration settings. Multi-agent v2 is still under development and OpenAI hasn't formally documented it yet. Developers, however, have observed changes made to Codex to accommodate the new agent plumbing – and some are concerned by the new arrangements. Last month, OpenAI devs merged a pull request (a suggested code change) to encrypt multi-agent v2 message payloads – the text instruction passed between agents. The pull request prefaces its explanatory text with the word "Why" but doesn't actually offer a reason for the change. It states: "Multi-agent v2 currently routes agent instructions through normal tool arguments and inter-agent context. That means the parent model can emit plaintext task text, Codex can persist it in history/rollouts, and the recipient can receive it as ordinary assistant-message JSON. "This changes the v2 path so agent instructions stay encrypted between model calls: Responses [An OpenAI API - Ed] encrypts the message argument returned by the model, Codex forwards only that ciphertext, and Responses decrypts it internally for the recipient model." A desire to enhance privacy and security, or conceal data that would be useful for model distillation, are sound reasons for these changes. Yet OpenAI has not said why it made the change. In the absence of clear communication from OpenAI, developers have urged the company to ensure that its implementation doesn't sacrifice auditability to accommodate other concerns. An issue opened by Ignat Remizov, CTO at payment service Zolvat, says, "The encrypted delivery path is understandable as privacy hardening, but it also removes the human-readable task/message text from local rollout history, trace reduction, and parent-side audit/debug surfaces." Remizov's concern is that developers and code maintainers will have less information to assess the instructions an agent received and the actions it took. "Guys, we don’t want to build Skynet and then be unable to audit what it’s doing," he quips. Other developers, echoing Remizov's concern about the loss of observability, speculate that OpenAI has locked its agent messaging down to keep competitors from seeing how its multi-agent implementation works. OpenAI did not immediately respond to a request for comment. ®

Ik stop bij het stoplicht op mijn dagelijkse forens en kijk om mij heen. E-bikes, normale fietsen, maar niemand met helm. Er komt een man aan fietsen, met helm.

Als je wel zin hebt om te sudokuen, maar het liever bij een gridje van 5x5 houdt.

Een kruiswoordpuzzel, maar dan heel klein (en snel).

Je krijgt een paar cijfers cadeau, maar het grid van 9x9 moet foutloos ingevuld worden.

Wie of wat staat er midden in het nieuws? Een actuele puzzel, die makkelijker is als je het nieuws een beetje volgt.

In het duel tussen twee voetbalgrootheden is Spanje superieur en valt het sterrenensemble van Frankrijk zwaar tegen. Voor de tweede keer in de geschiedenis bereikt Spanje de WK-finale.

A lawsuit from 26 Meta employees alleges the company used AI-driven scoring and monitoring systems to select workers for layoffs, disproportionately targeting employees with disabilities or those who had taken protected medical, family, pregnancy, or parental leave. "Meta did not assemble the termination list through the considered judgment of managers who knew the work. Instead, Meta used a constellation of internal artificial-intelligence systems -- including a system referred to internally as 'Metamate,' employee-trained 'second-brain' agents, keystroke- and activity-monitoring data, AI-token-usage dashboards, and algorithmically assisted performance ranking and calibration -- to score, rank, and select employees for inclusion on the list," the lawsuit (PDF) said. Ars Technica reports: Employees were allegedly graded, among other things, on how much they used Meta's AI tools. "Meta's internal dashboards classified employees by their stage of adoption of its artificial-intelligence tools, using categories such as 'AI Native,' 'AI First,' and 'AI Enabled,'" the lawsuit said. The lawsuit is apparently "the first against a major U.S. company to challenge the alleged use of AI in conducting layoffs," according to Reuters. The complaint alleges that Meta's tools for monitoring employees did not account for differences caused by disabilities and protected leaves. "Those tools draw on inputs -- performance ratings, calibration scores, productivity and output metrics, 'AI-native' ratings, and AI-token consumption -- that, by design, cannot be accumulated by an employee who is on protected medical or family leave, or whose output is reduced by a disability," the lawsuit said.

The lawsuit alleged that Meta management did not take steps to adjust scores for employees who took leave or who requested reasonable accommodations for disabilities. "Meta did not neutralize those inputs for protected leave; did not exclude protected-leave-takers or accommodation-seekers from the selection cohort; and did not pause the system for the individualized, leave- and accommodation-neutral review that the law requires," the complaint alleged. "The result was that employees who took protected leaves were disproportionately selected for layoff, based on scoring that not only failed to account for their protected leaves, but in effect penalized the employees for exercising their legal rights to these leaves." The 26 plaintiffs requested leaves or disability accommodations in the 24 months before being selected for layoffs, the lawsuit said. The layoffs are not yet finalized, but employees are scheduled to start losing their jobs on July 22, the lawsuit said. "These claims lack merit and are not based on facts," said Meta in a statement. "Workforce management and organizational decisions were and are made by people, not AI."

Read more of this story at Slashdot.

Weer voor Rotterdam 🌕 - 15-07-2026 01:15 CEST

In één oogopslag:
• 22.3°C · Helder 🌕 | Min 19.5°C / Max 30.4°C | Kans op neerslag 1%

Verwachting voor vandaag:
• Min 19.5°C, Max 30.4°C (Bewolkt) ☁️, Kans op neerslag 1%, 🧭 1021.1 hPa ➡️ 0.0 hPa/24h, Windsnelheid: 23.4 km/u (6.5 m/s), richting: ↙ 40°

Uurlijkse voorspelling voor de komende 12 uur:

• 02:00: 21.8°C (Helder) 🌕, 🧭 1021.3 hPa ➡️ 0.0 hPa/1h, Windsnelheid: 18.0 km/u (5.0 m/s), richting: ↙ 40°
• 03:00: 21.2°C (Helder) 🌕, 🧭 1021.1 hPa ➡️ 0.0 hPa/1h, Windsnelheid: 16.2 km/u (4.5 m/s), richting: ↙ 38°
• 04:00: 20.9°C (Helder) 🌕, 🧭 1021.0 hPa ➡️ 0.0 hPa/1h, Windsnelheid: 15.1 km/u (4.2 m/s), richting: ↙ 37°
• 05:00: 20.6°C (Helder) 🌕, 🧭 1021.2 hPa ➡️ 0.0 hPa/1h, Windsnelheid: 16.6 km/u (4.6 m/s), richting: ↙ 31°
• 06:00: 20.3°C (Zonnig) ☀️, 🧭 1021.4 hPa ➡️ 0.0 hPa/1h, Windsnelheid: 15.8 km/u (4.4 m/s), richting: ↙ 38°
• 07:00: 20.5°C (Zonnig) ☀️, 🧭 1021.6 hPa ➡️ 0.0 hPa/1h, Windsnelheid: 13.3 km/u (3.7 m/s), richting: ↙ 40°
• 08:00: 21.5°C (Zonnig) ☀️, 🧭 1021.7 hPa ➡️ 0.0 hPa/1h, Windsnelheid: 13.0 km/u (3.6 m/s), richting: ↙ 42°
• 09:00: 23.3°C (Zonnig) ☀️, 🧭 1022.0 hPa ➡️ 0.0 hPa/1h, Windsnelheid: 11.2 km/u (3.1 m/s), richting: ↙ 44°
• 10:00: 24.9°C (Zonnig) ☀️, 🧭 1022.2 hPa ➡️ 0.0 hPa/1h, Windsnelheid: 12.6 km/u (3.5 m/s), richting: ↙ 43°
• 11:00: 26.1°C (Zonnig) ☀️, 🧭 1022.1 hPa ➡️ 0.0 hPa/1h, Windsnelheid: 15.1 km/u (4.2 m/s), richting: ↙ 47°
• 12:00: 27.3°C (Zonnig) ☀️, 🧭 1021.9 hPa ➡️ 0.0 hPa/1h, Windsnelheid: 16.2 km/u (4.5 m/s), richting: ↙ 58°
• 13:00: 28.4°C (Zonnig) ☀️, 🧭 1021.7 hPa ➡️ 0.0 hPa/1h, Windsnelheid: 16.9 km/u (4.7 m/s), richting: ↙ 60°

Voorspelling voor de komende dagen:

• donderdag 16 juli: Min 20.3°C, Max 30.2°C (Zonnig) ☀️, 🧭 1018.6 hPa ↘️ -2.5 hPa/24h, Windsnelheid: 22.7 km/u (6.3 m/s), richting: ↙ 43°
• vrijdag 17 juli: Min 20.8°C, Max 27.2°C (Bewolkt) ☁️, Kans op neerslag 3%, 🧭 1014.1 hPa ↘️ -4.5 hPa/24h, Windsnelheid: 15.1 km/u (4.2 m/s), richting: ↙ 41°
• zaterdag 18 juli: Min 18.0°C, Max 25.4°C (Bewolkt) ☁️, Kans op neerslag 8%, 🧭 1017.7 hPa ↗️ +3.6 hPa/24h, Windsnelheid: 17.8 km/u (4.9 m/s), richting: ↘ 337°
• zondag 19 juli: Min 16.7°C, Max 20.9°C (Bewolkt) ☁️, Kans op neerslag 3%, 🧭 1021.1 hPa ↗️ +3.4 hPa/24h, Windsnelheid: 18.3 km/u (5.1 m/s), richting: ↘ 328°
• maandag 20 juli: Min 15.7°C, Max 20.4°C (Bewolkt) ☁️, Kans op neerslag 4%, 🧭 1023.0 hPa ↗️ +1.9 hPa/24h, Windsnelheid: 17.9 km/u (5.0 m/s), richting: ↘ 335°
• dinsdag 21 juli: Min 15.5°C, Max 20.6°C (Lichte motregen) 🌦️, Neerslag 0.3 mm, Kans op neerslag 6%, 🧭 1024.5 hPa ↗️ +1.5 hPa/24h, Windsnelheid: 15.7 km/u (4.4 m/s), richting: ↓ 342°

Details:
• 🌡️ Huidige temperatuur (om 01:15): 22.3°C (Helder)
• 🤚 Gevoelstemperatuur: 21.2°C (-1.1°C)
• 💨 Windsnelheid: 18.4 km/u (5.1 m/s), richting: ↙ 39°
• 🌬️ Windstoten: 34.6 km/h (9.6 m/s)
• 💧 Luchtvochtigheid: 70%
• 🧭 Luchtdruk: 1021.3 hPa ➡️ 0.0 hPa/3h
• 👁️ Zichtbaarheid: 19.7 km
• ☀️ UV-index: 0.0
• 🌅 Zonsopgang: 05:39 · 🌇 Zonsondergang: 21:56

Luchtkwaliteit:
• AQI: 41 🟢 (Goed)
• PM2.5: 5.8 μg/m³
• PM10: 8.8 μg/m³

Gegevens geleverd door Open-Meteo

#Rotterdam #Meteo #MeteoBot #MeteoNetherlands #OpenMeteo #FediMeteo

Thomas Hawk posted a photo:

Thomas Hawk posted a photo: