Amazon says it is ending sideloading on new Fire Sticks because "apps that facilitate piracy, and other apps, can carry malware," adding that there is "a good amount of evidence" that sideloaded apps may contain unwanted code or behavior. However, the company did not provide specific examples of Fire Stick users being harmed. Ars Technica reports: Amazon has released two Fire Stick models that use its proprietary, Linux-based operating system, Vega OS. Previous Fire Sticks ran Fire OS, which is an Android fork based on the Android Open Source Project. One of the biggest differences between Vega OS and Fire OS is that the former doesn't support sideloading. [...] In a recent interview, Or Goren, editor-in-chief of Cord Busters, a UK-based streaming news outlet, noted the negative reaction to Vega being a closed OS. [Aidan Marcuss, VP of Fire TV, advertising, and Appstore] responded, per the publication, by saying that Vega OS was Amazon's opportunity to "innovate and deliver more capabilities, even on the least expensive devices."

He also said that making a platform around security and privacy was "sort of utmost in my mind." The statement is somewhat ironic, considering Vega OS blocks custom launchers and other third-party apps that helped users avoid Amazon tracking and ads. Goren asked whether Amazon had evidence that sideloaded devices caused users harm. "Apps that facilitate piracy, and other apps, can carry malware," Marcuss responded. Marcuss also said that there is "a good amount of evidence that apps can carry unwanted code and behavior on them when they're sideloaded."

Marcuss didn't provide specific examples of Fire Stick users being hurt by sideloaded apps. There are some potential examples, though. In 2025, Amazon claimed to blacklist (which blocked the apps from being sideloaded to Fire Sticks) four video streaming apps for malicious behavior. At the time, AFTVnews reported that two of the apps served as residential proxy providers and were considered riskware, and that the other two had APK files that were flagged by virus-scanning tools. Safari and Chrome also flagged one of the apps' official websites, the publication reported. And in 2018, a botnet that infected Android devices with cryptocurrency-mining malware appeared on some Fire Sticks, per discussion on XDA Forums. That said, Amazon also has a history of disabling apps that let users circumnavigate its home screen that Fire devices, including Fire Sticks and Fire TVs, have increasingly used for ads. Worth noting: developers can continue sideloading apps onto Vega OS devices if they register them with Amazon.

Read more of this story at Slashdot.

Google has shut down the Tenor API, breaking GIF pickers in services that still relied on it and forcing platforms such as X to migrate elsewhere. 9to5Google notes that the library itself remains available at Tenor.com and "integrations within Google products are also still active, including Gboard, Google Messages, and more." From the report: The Tenor API has been rejecting new API sign-ups in January of this year, but existing integrations remained in place. This week, though, they're shutting down, and any integrations that remain in place will stop working on July 1. The support page adds details that "any API or Ads Distribution Agreements" with Tenor will be terminated on June 30, while "current integrations" will be "fully decommissioned" as of June 30.

One of the most notable examples here is Twitter/X, which has relied on Tenor for its GIF picker for years. Twitter/X Head of Product Nikita Bier confirmed that the platform has migrated elsewhere, which is why the "recently used" section was purged, and why you might notice fewer GIF options when posting. Other platforms affected include Discord, WhatsApp, and Bluesky.

Read more of this story at Slashdot.

California's Protect Our Games Act, which would require publishers to warn players before shutting down paid online games and offer refunds or continued access, failed to advance after a state Senate committee vote. Four state senators voted in favor, three voted against, and four abstained. Engadget reports: The committee unanimously voted in favor of granting the bill reconsideration, meaning it could come back before this group of state senators. Assemblymember Chris Ward introduced the bill in February and it passed the California State Assembly 43-16 in late May. That said, the abstentions prevented the bill's progression for now. "Not enough yeses means the bill stops here for this session," a volunteer with the Stop Killing Games campaign (which supported the bill) noted on Reddit. "That is the loss."

The volunteer also claimed this was the movement's first attempt to nudge such legislation through in the U.S., and that the bill got this far without paid staff or an in-person lobbying campaign. They said the Entertainment Software Association -- a trade organization of major game industry publishers -- brought in a lobbyist to halt the bill's progress (including by claiming private servers for the likes of Minecraft would be "illegal") and that Stop Killing Games would be more prepared to counter that in the future.

"Next session, we come back with an in-person lobbying presence, the funding to do this properly and a long list of organizations and developers signed on in support," the volunteer, u/Mr_Presidentle, wrote. "We are not limiting this to California. We intend to introduce versions of this in other state legislatures, and we are seriously looking at the federal level."

Read more of this story at Slashdot.

"Another breach at Tata has leaked details about Apple's iPhone 18, along with documents belonging to several other Tata clients," writes Longtime Slashdot reader Ritz_Just_Ritz. "It's becoming a recurring theme for the company." Reuters reports: Reuters has previously reported the Tata Electronics leak of more than 200,000 files on the dark web by World Leaks had files with purported component design papers of older iPhones and some parts of Tesla -- both Tata clients. They also included documents of Taiwan Semiconductor Manufacturing Co and Qualcomm, both of which make parts used in iPhones. New documents reviewed by Reuters show there are at least six files that map many components in the iPhone 18 Pro models to the specific company that supplies them. These include details of chips on its main circuit board and parts of the battery and cameras.

Apple considers this detail sensitive and is concerned about the documents being shared on the dark web as they relate to unreleased models, according to the person familiar with the matter. The data maps suppliers to iPhone parts, which Apple does not disclose in its public database of suppliers, the person added. In all, the documents detail hundreds of parts to be on the upcoming iPhone 18 Pro models. The records also show where Apple draws a part from several suppliers and where it relies on just a few, laying bare both its bargaining leverage and its vulnerabilities. More broadly, the leak threatens Apple's trust in Tata just as Tata is becoming central to its effort to shift iPhone production away from China. With India expected to produce roughly a quarter of the world's iPhones in 2026, any deterioration in that relationship could complicate Apple's diversification strategy and force tighter security controls across its suppliers.

Read more of this story at Slashdot.

⚽️ Kick-off time: 7pm local/11am AEST/2am BST/9pm EDT
⚽️ Player guide | Bracketology | Golden Boot | Mail Jonathan

Mexico’s football culture dates back to the early 20th century, and the country has a place in history as participants in the first ever World Cup match, when they lost 4-1 to France on the opening day of the 1930 World Cup in Uruguay.

The following match against Chile they conceded the World Cup’s first own-goal.

Continue reading...

Local officials said preliminary reports showed the centre was unregistered and operating inside a privately owned residential building

Fourteen children died after ⁠the roof of a tutoring centre collapsed in Pakistan’s eastern city of ⁠Lahore on Tuesday, ⁠rescue ​officials have said, as authorities opened the way for a possible negligence ⁠investigation.

Punjab’s emergency service said rescuers found children and a 30-year-old female teacher ⁠under the rubble of the private after-school facility. The ​children killed were aged ‌five to ‌16 with most below nine.

Continue reading...

• Coach accepts expectation that his side must win last-32 tie

• Spence set to start at right-back in place of injured Quansah

Thomas Tuchel has warned that England will reach the glamorous part of the World Cup only if they remember not to panic when they face the Democratic Republic of the Congo (DRC) in the last 32.

Although the German knows his side are heavy favourites to go through in Atlanta on Wednesday afternoon, he is wary of the threat posed by the DRC. England will be under pressure to break down a low block for the third time in four games and Tuchel is keen not to let anyone think a successful group stage is cause for celebration.

Continue reading...

When people form memories of the World Cup, it’s matches like this that do it. France once again won comprehensively, and against decent opposition, but the quality of their attacking play, and the sheer beauty of their goals, were difficult to fully appreciate in the moment. It’s the sort of thing that only comes into true focus upon reflection.

Kylian Mbappé drew alongside Lionel Messi in the race for the golden boot here with another brace of unerring finishes. Michael Olise should have had a hat-trick but made do with two assists and a virtuoso performance that left jaws across the floor of the New York-New Jersey stadium. At this point it is very hard to see beyond Didier Deschamps’ men, and there is equally the sense that there is more to come.

Continue reading...

We look at the betting markets to see who bookmakers expect to win at Silverstone.

Frankrijk heeft overtuigend gewonnen van Zweden in de zestiende finales van het WK. Het werd 3-0. Kylian Mbappé scoorde twee keer. De andere Franse treffer was van Bradley Barcola.

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

In één oogopslag:
• 17.3°C · Helder 🌕 | Min 16.7°C / Max 21.0°C | Kans op neerslag 13%

Verwachting voor vandaag:
• Min 16.7°C, Max 21.0°C (Bewolkt) ☁️, Kans op neerslag 13%, 🧭 1021.3 hPa ➡️ 0.0 hPa/24h, Windsnelheid: 12.2 km/u (3.4 m/s), richting: ↘ 298°

Uurlijkse voorspelling voor de komende 12 uur:

• 02:00: 16.7°C (Helder) 🌕, 🧭 1020.9 hPa ➡️ 0.0 hPa/1h, Windsnelheid: 6.8 km/u (1.9 m/s), richting: ↘ 330°
• 03:00: 16.8°C (Helder) 🌕, 🧭 1020.7 hPa ➡️ 0.0 hPa/1h, Windsnelheid: 4.3 km/u (1.2 m/s), richting: → 266°
• 04:00: 17.1°C (Gedeeltelijk bewolkt) ☁️, 🧭 1020.3 hPa ➡️ 0.0 hPa/1h, Windsnelheid: 6.8 km/u (1.9 m/s), richting: ↗ 204°
• 05:00: 16.9°C (Helder) 🌕, 🧭 1020.2 hPa ➡️ 0.0 hPa/1h, Windsnelheid: 7.9 km/u (2.2 m/s), richting: ↑ 199°
• 06:00: 16.7°C (Zonnig) ☀️, 🧭 1020.3 hPa ➡️ 0.0 hPa/1h, Windsnelheid: 9.0 km/u (2.5 m/s), richting: ↗ 205°
• 07:00: 17.0°C (Zonnig) ☀️, 🧭 1020.4 hPa ➡️ 0.0 hPa/1h, Windsnelheid: 9.7 km/u (2.7 m/s), richting: ↗ 214°
• 08:00: 18.2°C (Zonnig) ☀️, 🧭 1020.6 hPa ➡️ 0.0 hPa/1h, Windsnelheid: 9.0 km/u (2.5 m/s), richting: ↗ 224°
• 09:00: 20.0°C (Zonnig) ☀️, Kans op neerslag 1%, 🧭 1020.9 hPa ➡️ 0.0 hPa/1h, Windsnelheid: 7.9 km/u (2.2 m/s), richting: ↗ 245°
• 10:00: 21.7°C (Zonnig) ☀️, Kans op neerslag 3%, 🧭 1021.3 hPa ➡️ 0.0 hPa/1h, Windsnelheid: 5.4 km/u (1.5 m/s), richting: → 277°
• 11:00: 23.2°C (Zonnig) ☀️, Kans op neerslag 10%, 🧭 1021.5 hPa ➡️ 0.0 hPa/1h, Windsnelheid: 5.8 km/u (1.6 m/s), richting: ↘ 306°
• 12:00: 24.4°C (Zonnig) ☀️, Kans op neerslag 29%, 🧭 1021.5 hPa ➡️ 0.0 hPa/1h, Windsnelheid: 10.4 km/u (2.9 m/s), richting: ↘ 332°
• 13:00: 25.1°C (Zonnig) ☀️, Kans op neerslag 54%, 🧭 1021.4 hPa ➡️ 0.0 hPa/1h, Windsnelheid: 11.9 km/u (3.3 m/s), richting: ↘ 315°

Voorspelling voor de komende dagen:

• donderdag 02 juli: Min 16.7°C, Max 25.6°C (Gedeeltelijk bewolkt) ⛅, Kans op neerslag 13%, 🧭 1021.1 hPa ➡️ 0.0 hPa/24h, Windsnelheid: 18.0 km/u (5.0 m/s), richting: → 285°
• vrijdag 03 juli: Min 17.7°C, Max 21.8°C (Lichte motregen) 🌦️, Neerslag 0.4 mm, Kans op neerslag 26%, 🧭 1026.7 hPa ↗️ +5.6 hPa/24h, Windsnelheid: 25.9 km/u (7.2 m/s), richting: → 270°
• zaterdag 04 juli: Min 15.5°C, Max 20.2°C (Bewolkt) ☁️, Kans op neerslag 1%, 🧭 1026.2 hPa ↘️ -0.5 hPa/24h, Windsnelheid: 14.0 km/u (3.9 m/s), richting: ↘ 293°
• zondag 05 juli: Min 14.9°C, Max 23.9°C (Gedeeltelijk bewolkt) ⛅, Kans op neerslag 6%, 🧭 1021.8 hPa ↘️ -4.4 hPa/24h, Windsnelheid: 19.2 km/u (5.3 m/s), richting: ↗ 246°
• maandag 06 juli: Min 17.9°C, Max 22.6°C (Lichte motregen) 🌦️, Neerslag 0.3 mm, Kans op neerslag 13%, 🧭 1019.1 hPa ↘️ -2.7 hPa/24h, Windsnelheid: 17.5 km/u (4.9 m/s), richting: → 280°
• dinsdag 07 juli: Min 18.9°C, Max 21.8°C (Lichte motregen) 🌦️, Neerslag 0.6 mm, Kans op neerslag 19%, 🧭 1019.3 hPa ➡️ 0.0 hPa/24h, Windsnelheid: 18.0 km/u (5.0 m/s), richting: → 289°

Details:
• 🌡️ Huidige temperatuur (om 01:15): 17.3°C (Helder)
• 🤚 Gevoelstemperatuur: 15.8°C (-1.5°C)
• 💨 Windsnelheid: 5.0 km/u (1.4 m/s), richting: ↘ 302°
• 🌬️ Windstoten: 9.0 km/h (2.5 m/s)
• 💧 Luchtvochtigheid: 67%
• 🧭 Luchtdruk: 1020.9 hPa ↘️ -0.6 hPa/3h
• 👁️ Zichtbaarheid: 50.0 km
• ☀️ UV-index: 0.0
• 🌅 Zonsopgang: 05:26 · 🌇 Zonsondergang: 22:05

Luchtkwaliteit:
• AQI: 47 🟢 (Goed)
• PM2.5: 12.7 μg/m³
• PM10: 21.5 μg/m³

Gegevens geleverd door Open-Meteo

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

Weezer

Michel Polnareff

Editorial illustrations for Ruch Muzyczny ("Musical Movement").

Claude Code users are reporting that the app is silently deleting conversation transcripts – yours may even already be gone if you don’t know to change a default setting that the platform never bothers to tell users about. Claude Code’s GitHub repo features multiple open issues from the past couple of months, as users of the coding tool are finding their conversation transcripts gone. The problem appears to come down to the cleanupPeriodDays configuration option, which defaults to 30 days and runs every time Claude Code starts up, wiping out any .jsonl file it finds that isn’t fresh enough. Anthropic suggested the blame lies with users for not checking the documentation, telling The Register that the 30-day erasure policy has been there since Claude's launch as a security measure, and is documented. "Keeping plain text transcripts of coding sessions on disk indefinitely creates real security and privacy risks, since they can contain source code, credentials, and other sensitive material," the company said in a statement. "The 30-day default balances the ability to resume recent work against not holding that data on disk longer than needed. This has been part of Claude Code's design since launch as a security measure." This might not be such a huge deal if Claude Code bothered to inform 8naware users that their 30-day-old conversations with the bot would be wiped out the next time they opened the application, or informed them that the setting exists. But users are saying that's not the case. “Cleanup runs out of the box with no install-time disclosure or first-run dialog,” GitHub user FTSBrand wrote in his original post, which has since become the issue of record. “Users who treat their conversation history as durable working knowledge are silently mistaken about the persistence model.” Another user in their own issue thread reports that code and git history for a project remained after the cleanup wipe, “but the reasoning trail - design discussions, debugging context, analysis - is gone.” “For research work that context is the artifact,” GitHub user joekhochstetter said. This cleanup feature appears to bypass any form of recovery, with no soft-deletion option, grace period, or option to restore. User reports also suggest there’s no log of what’s deleted either, leaving people with no way to confirm what’s been wiped after it happens. Moreover, one might assume that simply changing the retention period to a higher number would render the issue irrelevant, but several users say setting a large value for retention isn’t working properly. GitHub user ojura’s root cause analysis suggests that’s because deletion is keyed to a transcript’s mtime (modification time) rather than its actual last activity timestamp. "Because mtime is externally mutable, anything that touches it flips the outcome: a restore, a sync client, or a script that sets mtimes to a session's true (old) last-activity date makes a present session look old, and it is silently deleted on the next sweep,” ojura explained. The only solution in the thread is to ensure Claude Code transcripts are backed up, with several different iterations of such a workaround suggested. That hasn’t been enough to satisfy some Claude Coders - they want it fixed. “Backups are good hygiene, but they don't replace product-level disclosure/provenance for a destructive retention sweep,” writes GitHub user caioribeiroclw-pixel. ®

Thomas Hawk posted a photo:

Thomas Hawk posted a photo: