Al drie maanden lang ligt er een ongeopend pakketje in de lade van mijn bureau. Daarin een snurkbeugel.

Plaats de cijfers 1 tot en met 9 zo in het diagram dat elk cijfer precies één keer voorkomt in elke rij, kolom, de negen vetomrande 3x3 vakken, én de vier grijze 3x3 vakken.

Horizontaal: 1. ‘Voorjaarstrek zit erop, dus vis__ staat weer uit’ 6. Russische clown 9. Delen de kaarten uit 10. Vol(komen in de weer) 11. Daarvan komt de wind fel aan 14.

Arrest warrant issued for bombing suspect who will soon be subject of an Interpol Red Notice

A suspect has been identified in the investigation into a parcel bombing that seriously wounded a sanctioned Ukraine-born multimillionaire and two others in Monaco, the principality’s prosecutor’s office said Thursday.

“An arrest warrant has been issued for the suspect, who will be the subject of an Interpol Red Notice from this evening,” the prosecutor’s office added.

Continue reading...

• Coach Hossam Hassan unsure whether veteran will start

• ‘Messi isn’t that tall’: Pharaohs not worried by physical Australia

The Socceroos are set to face Mo Salah in their last 32 match, though uncertainty hangs over whether the Egypt great will start the World Cup knockout in Dallas or come off the bench.

Salah was seen training with his teammates on Thursday and Egypt coach Hossam Hassan confirmed his “passionate” forward was fit enough to play.

Continue reading...

President, in latest AI-generated social media post, targets prominent celebrities who have spoken out against him

Donald Trump on Thursday posted an AI-generated social media video portraying himself as a doctor who claims to have cured some of his most prominent celebrity critics – including Rosie O’Donnell – of the fictional condition “Trump derangement syndrome”.

Outside the AI fantasy, O’Donnell said her assessment of the president remained unchanged. In a statement, she offered her own diagnosis: “He’s quite ill-and getting worse daily. The 25th amendment exists for exactly this reason. Remove. Impeach. Convict.”

Continue reading...

The US unemployment rate fell to 4.2% in June largely because 720,000 people left the labor force, pushing participation to 61.5%. Excluding the Covid-era jobs market, that's the lowest participation rate since June 1976. CNBC reports: The decline in the labor force marks a "massive exodus" driven by multiple factors, said Mike Reid, head of U.S. economics at RBC. "The unemployment rate fell to 4.2% as both the number of unemployed workers and the size of the labor force pulled back," Reid wrote in a post-report commentary. "This may well be a story of retirements but could also be a story of prior job seekers dropping out of the labor force."

[...] [T]he rolls of those counted as not in the labor force, a group that includes the unemployed and those not looking for work, jumped by 832,000. And while the establishment survey, which counts jobs filled, showed growth for the month of 57,000, the survey of households, which counts the actual level of those working, tumbled by 507,000. On a year-over-year basis, the labor force is down by just over 1 million, while the level of the employed also has fallen by 1.06 million and the ranks of the unemployed have risen by 40,000. The employment-to-population ratio slipped to 59% in June, the lowest since October 2021. All that has happened while the unemployment rate has risen by just one-tenth of a percentage point to 4.2%.

The drop in participation is sometimes attributed to a shrinking immigrant population and retiring baby boomers and Gen Xers. However, in June the biggest plunge came from what is defined as "prime age" workers, or those between the ages of 25 and 54. That rate fell 0.6 percentage point to 83.3%, its lowest since December 2023. "Looking at the statistics now, that argument doesn't hold up so well," North said of the retirement and immigration rationale. "I hate to use the word 'alarming,'" he added, but said the numbers are cause for concern.

Read more of this story at Slashdot.

Greg Adams Photography posted a photo:

Vienna, 2012

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

In één oogopslag:
• 16.9°C · Helder 🌕 | Min 17.0°C / Max 21.3°C | Kans op neerslag 32%

Verwachting voor vandaag:
• Min 17.0°C, Max 21.3°C (Matige motregen) 🌦️, Neerslag 1.7 mm, Kans op neerslag 32%, 🧭 1026.9 hPa ↗️ +1.8 hPa/24h, Windsnelheid: 24.5 km/u (6.8 m/s), richting: → 259°

Uurlijkse voorspelling voor de komende 12 uur:

• 02:00: 16.8°C (Helder) 🌕, 🧭 1025.1 hPa ➡️ 0.0 hPa/1h, Windsnelheid: 7.9 km/u (2.2 m/s), richting: → 275°
• 03:00: 16.7°C (Helder) 🌕, 🧭 1025.4 hPa ➡️ 0.0 hPa/1h, Windsnelheid: 8.3 km/u (2.3 m/s), richting: → 281°
• 04:00: 16.5°C (Helder) 🌕, 🧭 1025.5 hPa ➡️ 0.0 hPa/1h, Windsnelheid: 10.1 km/u (2.8 m/s), richting: → 283°
• 05:00: 16.1°C (Helder) 🌕, 🧭 1025.4 hPa ➡️ 0.0 hPa/1h, Windsnelheid: 10.1 km/u (2.8 m/s), richting: → 285°
• 06:00: 15.9°C (Zonnig) ☀️, 🧭 1025.8 hPa ➡️ 0.0 hPa/1h, Windsnelheid: 9.0 km/u (2.5 m/s), richting: → 283°
• 07:00: 17.1°C (Zonnig) ☀️, 🧭 1026.1 hPa ➡️ 0.0 hPa/1h, Windsnelheid: 9.0 km/u (2.5 m/s), richting: → 288°
• 08:00: 18.3°C (Zonnig) ☀️, 🧭 1026.4 hPa ➡️ 0.0 hPa/1h, Windsnelheid: 9.4 km/u (2.6 m/s), richting: ↘ 299°
• 09:00: 19.3°C (Licht bewolkt) 🌤️, 🧭 1026.8 hPa ➡️ 0.0 hPa/1h, Windsnelheid: 9.0 km/u (2.5 m/s), richting: → 282°
• 10:00: 20.0°C (Licht bewolkt) 🌤️, 🧭 1027.3 hPa ↗️ +0.5 hPa/1h, Windsnelheid: 11.9 km/u (3.3 m/s), richting: → 278°
• 11:00: 20.9°C (Zonnig) ☀️, 🧭 1027.4 hPa ➡️ 0.0 hPa/1h, Windsnelheid: 13.0 km/u (3.6 m/s), richting: → 281°
• 12:00: 21.6°C (Zonnig) ☀️, 🧭 1027.5 hPa ➡️ 0.0 hPa/1h, Windsnelheid: 14.8 km/u (4.1 m/s), richting: → 286°
• 13:00: 21.9°C (Zonnig) ☀️, 🧭 1027.7 hPa ➡️ 0.0 hPa/1h, Windsnelheid: 16.6 km/u (4.6 m/s), richting: → 291°

Voorspelling voor de komende dagen:

• zaterdag 04 juli: Min 15.9°C, Max 22.0°C (Bewolkt) ☁️, 🧭 1024.7 hPa ↘️ -2.2 hPa/24h, Windsnelheid: 18.0 km/u (5.0 m/s), richting: ↘ 293°
• zondag 05 juli: Min 17.6°C, Max 24.6°C (Bewolkt) ☁️, Kans op neerslag 3%, 🧭 1022.3 hPa ↘️ -2.4 hPa/24h, Windsnelheid: 20.9 km/u (5.8 m/s), richting: → 262°
• maandag 06 juli: Min 19.0°C, Max 22.4°C (Bewolkt) ☁️, Neerslag 0.2 mm, Kans op neerslag 6%, 🧭 1017.5 hPa ↘️ -4.8 hPa/24h, Windsnelheid: 16.6 km/u (4.6 m/s), richting: → 280°
• dinsdag 07 juli: Min 18.0°C, Max 24.0°C (Bewolkt) ☁️, Kans op neerslag 2%, 🧭 1016.8 hPa ↘️ -0.7 hPa/24h, Windsnelheid: 15.5 km/u (4.3 m/s), richting: → 283°
• woensdag 08 juli: Min 17.3°C, Max 23.7°C (Bewolkt) ☁️, Kans op neerslag 14%, 🧭 1022.2 hPa ↗️ +5.4 hPa/24h, Windsnelheid: 18.6 km/u (5.2 m/s), richting: ↘ 293°
• donderdag 09 juli: Min 17.2°C, Max 23.9°C (Bewolkt) ☁️, Kans op neerslag 1%, 🧭 1022.7 hPa ↗️ +0.5 hPa/24h, Windsnelheid: 9.9 km/u (2.8 m/s), richting: ↓ 350°

Details:
• 🌡️ Huidige temperatuur (om 01:15): 16.9°C (Helder)
• 🤚 Gevoelstemperatuur: 15.6°C (-1.3°C)
• 💨 Windsnelheid: 7.6 km/u (2.1 m/s), richting: → 286°
• 🌬️ Windstoten: 11.2 km/h (3.1 m/s)
• 💧 Luchtvochtigheid: 63%
• 🧭 Luchtdruk: 1025.1 hPa ➡️ 0.0 hPa/3h
• 👁️ Zichtbaarheid: 23.5 km
• ☀️ UV-index: 0.0
• 🌅 Zonsopgang: 05:27 · 🌇 Zonsondergang: 22:04

Luchtkwaliteit:
• AQI: 31 🟢 (Goed)
• PM2.5: 4.6 μg/m³
• PM10: 9.2 μg/m³

Gegevens geleverd door Open-Meteo

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

During a 48-hour period from June 7 to 8, developer Charles Jones's Google Cloud account registered $11,089.77 in charges - most related to the use of Gemini image-generation models. Yet Jones, a solo developer who runs programmatic SEO and insurance sites, told The Register that he doesn't have any workflow that generates AI images. Google suspended his account anyway. A suspension notification sent to Jones on June 7 justified the decision by stating his account "was engaged in abusive activity consistent with hijacked resources." "The root cause was attributed to a compromised firebase-adminsdk service account key," said Jones, who provided The Register with documentation of his exchanges with Google Cloud support. The notification advised Jones to report his concerns if he believed the account was compromised by a third party. He did so and took the steps required by Google to have his account reinstated. He disabled the service account and revoked the key. But the Google Cloud billing team has repeatedly refused to forgive the charges. As we reported previously, complaints about charges arising from fraudulent API key usage among Google Cloud customers are not uncommon. In February, a developer based in Vietnam claimed that a Google Cloud API key compromise had resulted in more than $82,000 in charges over 48 hours. A similar report claiming more than $10,000 in fraudulent charges surfaced a month later on Reddit. Regardless of where the fault lies – insecure practices by developers or insecure Google infrastructure – Google may choose to hold developers liable for unauthorized charges, even if the credit-card issuing bank has reversed the charge as fraudulent. At the same time, Google still hasn't publicly released a mechanism to cap Google Cloud spending. The company introduced Spend Caps for certain services as a private preview but hasn't made the service generally available. Other cost-limiting measures, like API-specific usage limits "aren't designed to act as a project-wide spending cap." Similarly, Budget Alerts "don't automatically prevent the use or billing of your services when the budget amount or threshold rules are met or exceeded." Google provides a workaround by allowing Budget Alert notifications to disable cloud billing, but warns that doing so means "resources might be irretrievably deleted." In March, Google introduced project spend caps for the Gemini API as an experimental feature, but at the same time the company said that spend caps have a 10 minute delay and customers are responsible for spending during that period – so the company's definition of cap is rather flexible. What's more, Google said its system "now automatically upgrades you to the next [usage] tier as your usage grows and your payment history matures." And higher tiers raise spending caps. This all means it can still be a challenge for Google Cloud customers to avoid unbounded financial obligations in the event of an account or API key compromise. Escaping that responsibility requires engaging with Google customer service in an opaque appeals process in which the company isn't required to demonstrate customer negligence or an audit trail. "Here's a question I can't get answered, and I think it's central to the whole pattern," Jones said. "Google's Trust & Safety was quick to alert me that a service account key was compromised — but I have been given no route, anywhere, to see HOW or WHERE that key was actually exposed. There is no trace, no log path, no forensic detail offered." Jones said he was the only person who had access to the VM where the compromised key resided and he insists that he followed the company's recommended security practices. "So how does a single-access VM produce a leaked service account key — and why is the burden on me to prove I secured something Google itself can't (or won't) show me how I failed to secure? Google is invoking its Shared Responsibility Model to deny the refund, but that model assumes a customer security failure Google has never demonstrated." The Register twice asked Google why it would deny a refund and what evidence it has that supports that decision. We've not heard back. ®