How Baban Hussain’s online hit, remixed by Australian producer, launched the Kurdish New Zealander to global fame

Two months ago, Baban Hussain, a 22-year-old Kurdish New Zealander, was working from a self-run studio in Auckland, putting out music to a few thousand followers as little-known rapper Fat Papi.

Then, as modern fairytales go, he made a viral hit that has amassed over 7.5bn views across YouTube, gained him nearly 10m new monthly listeners on Spotify, and catapulted him on to global charts – including the US Billboard Hot 100.

Continue reading...

Chow Hang-tung has been detained since 2021, and written about everything from clothes to Tiananmen Square and the meaning of freedom

• Tiananmen Square vigil organisers in Hong Kong found guilty of ‘inciting subversion’

In one essay written from prison, Chow Hang-tung worries about her hairstyle before court appearances because there are no combs or mirrors in her cell.

“In a place like prison, where anything that is personal is stripped away, it’s even more important to hold on to every means by which you can express yourself,” she writes. “Don’t let uniform, depersonalised rules, dress codes, schedules, and behavioural requirements grind down your edges and mould you into a ‘model citizen’”.

Continue reading...

After an underwhelming season, Arsenal have made major changes with club legends departing and top talent from all over Europe arriving

Guardian writers’ predicted position: 2nd (NB: this is not necessarily Suzanne Wrack’s prediction but the average of our writers’ tips)

Last season’s position: 2nd

Continue reading...

Saja El-Khawas had been in critical condition after being pulled from sea in West Sussex

A six-year-old girl has died in hospital three days after being pulled from the sea off Shoreham in West Sussex, in an incident that also killed her mother, father and sister.

Saja El-Khawas died on Friday after the deaths of her sister Sara El-Khawas, 14, and her parents Hassan El-Khawas, 55, and Zeina Alayn, 37, on Tuesday.

Continue reading...

De afgelopen weken genieten mijn man en ik van de mensen die we ontmoeten tijdens onze reis door het buitenland en hun uiteenlopende eetgewoonten.

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

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

Een Precies Vier bestaat uit 16 woorden, begrippen of namen, die moeten worden verdeeld in precies vier groepen van vier. Er is telkens maar één oplossing mogelijk. Welke woorden vormen een connectie?

One of the best ways to lower your AWS bill by 99 percent or more is by not checking your keys into public GitHub repositories. Many of us have done this inadvertently over the years, and the defenses against it have improved dramatically (my personal favorite being "using non-ephemeral credentials derived from OIDC or SSO is an anti-pattern"), but it still happens. On Friday, BleepingComputer reported on a Truffle Security finding that hundreds of leaked AWS keys are root keys and are somehow still active and valid. AWS Security is full of very smart people who care deeply about a number of things, including "not abetting crime." If they detect (usually via automated means) that a credential has been leaked, they're quick to apply a Quarantine Policy to it. Trouble is, that policy enumerates a bunch of bad behaviors in an ever-expanding graph of principals and associated behaviors. AWS' considered position on this is that they don't want to break customer environments: "The policy aims to limit the potential damage that may be caused by fraud-related activity leading to unauthorized charges, while not impacting the existing resources." AWS' considered position on this is wrong. If I get access to your credentials (much less a root credential, good god), deactivating them may very well break your workload because anything that relies on those credentials will start failing. Until you rotate them, those workloads will continue to fail. That's not good! But I promise you, as a bad actor, I can do far worse to you. Hold my tea Go ahead and apply a quarantine policy to a credential set and toss it my way. I won't be able to buy savings plans, read your S3 data, modify Lambda functions, and do a host of other things. But here's what I can do. Anything I damn well feel like on RDS. You don't have anything important in databases, right? ssm:SendCommand / ssm:StartSession are permitted, which means I can run commands as root on EC2 instances, which will in turn invoke with that instance role’s permissions. sts:AssumeRole means that I can assume any other role in the account and get its permissions, rendering the entire restriction list potentially moot. I can use autoscaling:CreateAutoScalingGroup / UpdateAutoScalingGroup to launch instances via the Auto Scaling service-linked role, so the ec2:RunInstances deny never applies. cloudtrail:LookupEvents gets denied (that'll stop you from... reading the audit log), but I can call both cloudtrail:StopLogging and DeleteTrail which do exactly what you expect; you don't have an audit log anymore. SES denies ses:GetSendQuota / ListIdentities actions, but y'know what's missing? SendEmail, so I can blast my spam out to your entire list. sns:GetSMSAttributes means I can't get your SMS configuration, but I can absolutely sns:Publish to send fraudulent text messages wherever I'd like. s3:DeleteObject gets denied, but s3:PutObject is allowed. I can't delete your data, but I can fill a bucket to petabytes. Next, they fail to block s3:PutBucketVersioning, s3:PutObjectLockConfiguration, s3:PutObjectRetention, and s3:PutObjectLegalHold. So on any existing bucket, like that one I just stuffed petabytes into, I can enable versioning, turn on Object Lock, and set a bucket-default COMPLIANCE-mode retention out to 2126, or alternatively slap it on per object. COMPLIANCE retention can't be shortened or removed by anyone, including the account root and AWS Support. The only way to remove it is to delete the entire AWS account. secretsmanager:GetSecretValue, ssm:GetParameter* (WithDecryption), and kms:Decrypt are all unencumbered, so your secrets are now my secrets. Sharing is good! Backups are important, so it's a shame you don't have any. Well, not after I kick off backup:DeleteRecoveryPoint / DeleteBackupVault, and rds:DeleteDBSnapshot. If you're using CloudFormation, and for some things you almost certainly are, cloudformation:DeleteStack going unmentioned means you're not using it anymore and all of your stacks are gone. I would make different choices This isn't a comprehensive list - just a few things that occurred to me over the course of about an hour. I'm not a bad actor; I'm almost positive that I'm missing a whole bunch. AWS is almost certainly going to change this. My question for them is simply, "how big of a customer incident needs to happen before you do?" ®

Nvidia has made its fortune on the AI boom, but the company has a problem. It faces a growing number of roadblocks which, if left unchecked, could pop the bubble. Thus, the AI arms dealer has been forced to play a game of Whac-a-Mole, shoring up the foundations of its empire by investing its spoils into ensuring its customers don’t stop buying. The latest example of this came Friday, when Nvidia announced it’d become a minority investor in Cloverleaf. Founded in 2024, Cloverleaf specializes in laying the literal foundations – by which we mean the land and power – necessary to build bit barns so they can be leased by the cloud providers and model devs that actually pay the bills for Nvidia’s hardware. Nvidia can only sell as many GPUs as there are datacenters to put them, and those datacenters can only be deployed where there’s adequate power to support them. And since its latest round of GPUs can’t just be dropped into any old bit barn, Nvidia is going to need a lot more datacenter capacity, and by extension a lot more power. A new breed of datacenter Up until 2024, the majority of Nvidia’s systems were air-cooled. Supercomputers, like those built by Cray and Eviden, were the exception to the rule. Unless you were deploying tens of thousands of GPUs, its accelerators could be deployed just about anywhere with minimal modification to the facility. That began to change with Nvidia’s Blackwell generation. You could still get air-cooled systems from Nvidia and its partners, and it certainly sold a lot of eight-way HGX B200 boxes, but deploying its most powerful NVL72 systems required liquid cooling that not every facility was capable of supplying. Liquid-cooled facilities are harder to build than their air-cooled counterparts. Liquid-cooled racks tend to be more compute dense, and therefore heavier and power hungry to operate. That means in addition to larger UPS backups and beefier PDUs, these facilities now need a bunch of coolant distribution units (CDUs) to pump coolant around — about one for every one to three megawatts of compute capacity. Datacenters must be designed to support all this extra weight, and the problem is only going to get thornier as Nvidia transitions from roughly 250kW to 600kW racks starting next year. With Nvidia’s Rubin generation of GPUs, air-cooled GPUs may as well be a thing of the past, at least in the HGX and NVL-style form factors that power the majority of AI training and inference deployments today. For the first time, Nvidia is offering the chips only in liquid-cooled varieties. So, to sell its next-generation GPUs, Nvidia not only needs its customers to have adequate capacity, but also needs those facilities to offer the right mix of power and cooling. Right sizing for deployment It’s well established that Nvidia prioritizes customers with datacenters ready to fill. However, many of the GPU-slinger's biggest customers don’t actually own datacenters, but instead lease capacity from others. For example, Crusoe built OpenAI’s Stargate facility in Abilene, Texas, and Oracle runs it. Altman and crew are simply supplying the demand. So, Nvidia has invested in model devs and neocloud partners by helping them get financing or even investing directly in their businesses. Nvidia’s investments in OpenAI, CoreWeave, and Nebius are just a few examples. That works so long as the bit barns available for rent are the right size and shape for the hardware. But, as we noted earlier, many existing facilities aren’t. To further reduce friction and make it easier for its customers to find space to deploy its kit, Nvidia introduced its DSX platform last fall and officially launched it this spring. In a nutshell, DSX is a set of blueprints outlining exactly how much power, cooling infrastructure, and space are needed to support a given amount of compute. It also provides tools to optimize that compute to minimize wasted capacity. The power problem But even designing to a spec won’t do bit barn builders any good if they can’t get their hands on enough power. The proliferation of AI datacenters has begun to strain grid capacity, forcing many new ones to employ behind-the-meter power generation. For example, Nebius has begun using Bloom Energy's natural gas fuel cells to power its datacenters, rather than relying entirely on existing grid infrastructure. Nvidia’s investment in Cloverleaf is the latest example of how the GPU slinger is using the circular AI economy to its advantage. The terms of the deal haven’t been disclosed, but the benefits are obvious: Cloverleaf gets an influx of cash, while Nvidia gets greater control over the build process. As part of the deal, Cloverleaf is also embracing Nvidia’s DSX spec. In theory, this should enable bit barn builders to drop a DSX-compliant datacenter on a Cloverleaf-supplied site and be serving customers without delay. For Cloverleaf, Nvidia’s spec includes a wealth of power-related capabilities, including DSX Flex, which allows datacenters to scale back their workloads in response to grid conditions. So if grid demand spikes during a heat wave because everyone’s AC just kicked on, datacenters know it’s probably not a good idea to kick off another training run. The tech can also be used to offload demand onto onsite power generation or storage systems, like batteries — all things a company tasked with supplying powered sites for datacenters might be interested in. The deal is the latest example of how Nvidia is using its war chest to shore up cracks in the broader AI ecosystem before they become a problem. We wrote a few weeks ago about how the company was helping AI infrastructure startups secure financing in exchange for a share of the revenues, but it's now clear Nvidia is attacking potential roadblocks from every angle. ®

Weer voor Rotterdam ☁️ - 22-08-2026 01:15 CEST

In één oogopslag:
• 17.3°C · Gedeeltelijk bewolkt ☁️ | Min 16.0°C / Max 20.7°C | Kans op neerslag 38%

Verwachting voor vandaag:
• Min 16.0°C, Max 20.7°C (Matige motregen) 🌦️, Neerslag 1.5 mm, Kans op neerslag 38%, 🧭 1018.9 hPa ↗️ +4.6 hPa/24h, Windsnelheid: 15.1 km/u (4.2 m/s), richting: ↘ 318°

Uurlijkse voorspelling voor de komende 12 uur:

• 02:00: 16.8°C (Helder) 🌕, Kans op neerslag 27%, 🧭 1014.3 hPa ➡️ 0.0 hPa/1h, Windsnelheid: 5.8 km/u (1.6 m/s), richting: ↘ 330°
• 03:00: 16.7°C (Gedeeltelijk bewolkt) ☁️, Kans op neerslag 28%, 🧭 1014.5 hPa ➡️ 0.0 hPa/1h, Windsnelheid: 4.3 km/u (1.2 m/s), richting: ↘ 299°
• 04:00: 16.6°C (Bewolkt) ☁️, Kans op neerslag 27%, 🧭 1014.7 hPa ➡️ 0.0 hPa/1h, Windsnelheid: 5.8 km/u (1.6 m/s), richting: → 292°
• 05:00: 16.3°C (Helder) 🌕, Kans op neerslag 31%, 🧭 1015.0 hPa ➡️ 0.0 hPa/1h, Windsnelheid: 9.0 km/u (2.5 m/s), richting: ↘ 302°
• 06:00: 15.3°C (Bewolkt) ☁️, Kans op neerslag 47%, 🧭 1015.6 hPa ↗️ +0.6 hPa/1h, Windsnelheid: 10.4 km/u (2.9 m/s), richting: ↓ 353°
• 07:00: 15.1°C (Lichte motregen) 🌦️, Neerslag 0.2 mm, Kans op neerslag 68%, 🧭 1015.9 hPa ➡️ 0.0 hPa/1h, Windsnelheid: 9.0 km/u (2.5 m/s), richting: ↓ 342°
• 08:00: 15.6°C (Bewolkt) ☁️, Kans op neerslag 84%, 🧭 1016.8 hPa ↗️ +0.9 hPa/1h, Windsnelheid: 5.0 km/u (1.4 m/s), richting: ↓ 356°
• 09:00: 17.1°C (Zonnig) ☀️, Kans op neerslag 91%, 🧭 1017.6 hPa ↗️ +0.8 hPa/1h, Windsnelheid: 5.0 km/u (1.4 m/s), richting: ↘ 319°
• 10:00: 15.8°C (Bewolkt) ☁️, Kans op neerslag 94%, 🧭 1018.3 hPa ↗️ +0.7 hPa/1h, Windsnelheid: 18.7 km/u (5.2 m/s), richting: ↓ 348°
• 11:00: 15.1°C (Lichte motregen) 🌦️, Neerslag 0.2 mm, Kans op neerslag 94%, 🧭 1018.9 hPa ↗️ +0.6 hPa/1h, Windsnelheid: 10.1 km/u (2.8 m/s), richting: ↙ 42°
• 12:00: 16.8°C (Bewolkt) ☁️, Kans op neerslag 94%, 🧭 1019.3 hPa ➡️ 0.0 hPa/1h, Windsnelheid: 4.0 km/u (1.1 m/s), richting: ↙ 57°
• 13:00: 18.4°C (Licht bewolkt) 🌤️, Kans op neerslag 92%, 🧭 1019.6 hPa ➡️ 0.0 hPa/1h, Windsnelheid: 15.1 km/u (4.2 m/s), richting: ↘ 333°

Voorspelling voor de komende dagen:

• zondag 23 augustus: Min 15.1°C, Max 19.9°C (Lichte motregen) 🌦️, Neerslag 0.4 mm, Kans op neerslag 41%, 🧭 1024.4 hPa ↗️ +5.5 hPa/24h, Windsnelheid: 18.7 km/u (5.2 m/s), richting: ↘ 335°
• maandag 24 augustus: Min 15.5°C, Max 20.5°C (Bewolkt) ☁️, Kans op neerslag 2%, 🧭 1022.1 hPa ↘️ -2.3 hPa/24h, Windsnelheid: 15.8 km/u (4.4 m/s), richting: ↘ 335°
• dinsdag 25 augustus: Min 14.4°C, Max 20.1°C (Bewolkt) ☁️, Kans op neerslag 2%, 🧭 1014.1 hPa ↘️ -8.0 hPa/24h, Windsnelheid: 14.0 km/u (3.9 m/s), richting: ← 81°
• woensdag 26 augustus: Min 13.6°C, Max 20.3°C (Bewolkt) ☁️, Kans op neerslag 7%, 🧭 1012.2 hPa ↘️ -1.9 hPa/24h, Windsnelheid: 13.6 km/u (3.8 m/s), richting: ← 82°
• donderdag 27 augustus: Min 15.5°C, Max 22.9°C (Lichte motregen) 🌦️, Neerslag 0.9 mm, Kans op neerslag 28%, 🧭 1009.1 hPa ↘️ -3.1 hPa/24h, Windsnelheid: 8.4 km/u (2.3 m/s), richting: ↖ 114°
• vrijdag 28 augustus: Min 18.0°C, Max 24.8°C (Lichte onweersbui) ⛈️, Neerslag 6.6 mm, Kans op neerslag 44%, 🧭 1006.2 hPa ↘️ -2.9 hPa/24h, Windsnelheid: 13.9 km/u (3.9 m/s), richting: ↖ 147°

Details:
• 🌡️ Huidige temperatuur (om 01:15): 17.3°C (Gedeeltelijk bewolkt)
• 🤚 Gevoelstemperatuur: 16.0°C (-1.3°C)
• 💨 Windsnelheid: 6.8 km/u (1.9 m/s), richting: ↓ 350°
• 🌬️ Windstoten: 12.2 km/h (3.4 m/s)
• 💧 Luchtvochtigheid: 66%
• 🧭 Luchtdruk: 1014.3 hPa ➡️ 0.0 hPa/3h
• 👁️ Zichtbaarheid: 50.0 km
• ☀️ UV-index: 0.0
• 🌅 Zonsopgang: 06:36 · 🌇 Zonsondergang: 20:54

Luchtkwaliteit:
• AQI: 25 🟢 (Goed)
• PM2.5: 4.2 μg/m³
• PM10: 8.5 μg/m³

Gegevens geleverd door Open-Meteo

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

Federal prosecutors have charged activist Samuel Tunick with obstruction after he gave Customs and Border Protection officers a duress passcode that wiped his GrapheneOS-powered Pixel during a border search. "His prosecution is one of the earliest known instances of the federal authorities charging a person with destroying evidence using a program designed to wipe a device clean after a specific code is entered," reports The New York Times. From the report: "Obstructing federal law enforcement is a serious matter that has serious repercussions," Theodore Hertzberg, the U.S. attorney for the Northern District of Georgia, said in a statement. "Individuals who destroy or attempt to destroy property, including data, to prevent lawful search and seizure should expect to face prosecution and punishment for their actions."

A spokeswoman for U.S. Customs and Border Protection said in a statement that the agency had the authority to search the electronic devices of anyone entering or leaving the United States, regardless of citizenship, to enforce laws addressing terrorism, child exploitation, drug- and human-smuggling, visa fraud and national security threats.

"The border search will only include an examination of information that is present on the device at the time it is presented for inspection," the spokeswoman said, adding that it searched the electronic devices of fewer than 0.01 percent of all arriving international travelers in the last fiscal year. "Just the knowledge that the government is peering into your private life in this way, trying to dig up dirt on you, even though it's unsuccessful, is creepy," Tunick said, in response to a question about how the charges have affected him.

His message: "The government doesn't own our communications, our relationships, as hard as they might try to. We have to defend our fundamental right to privacy; otherwise we can't say that we really live in a democracy."

Read more of this story at Slashdot.