Urgent.News

What's breaking now, across thousands of outlets.

Tech

Apple joins Google in renaming Lake Ontario 'Lake America'

Apple Maps now shows Lake Ontario as "Lake America" for US users, following Google's lead in complying with US President Donald Trump's order as trade talks with Canada sour.

Apple has changed the name of Lake Ontario to "Lake America" on its Maps app for users in the United States. This follows a similar move by Google after US President Donald Trump's executive order to rename the lake. According to Dawn, the change was made after the lake's name was updated in the US Geographic Names Information System.

The renaming applies only to US users, while Canadian users will still see "Lake Ontario". Users in the rest of the world will see both names, as reported by several outlets including Dawn and Malay Mail. This approach is similar to one used by Apple after Trump renamed the Gulf of Mexico as the "Gulf of America".

The move highlights how US tech companies are being pulled into geopolitical disputes, as the Trump administration pressures them to comply with executive orders that have been rejected by allies and international bodies. According to Malay Mail, a majority of Americans oppose Trump's moves, including the renaming of Lake Ontario.

Brief written by urgent.news from Euronews, Dawn, Arutz Sheva - Israel National News, Bernama, Malay Mail — 5 reports on this story. Machine-written — may contain errors; check the original before relying on it.

Also reported by 1 other outlet

Read the original at euronews.com →

More in Tech

Krypton MCP – Securing Local LLMs and MCP Tools with Zero-Trust Proxy in Go

Connecting local or cloud LLMs directly to databases, filesystems, and internal APIs via Model Context Protocol (MCP) creates a massive attack surface.

  • Krypton MCP secures local LLMs with zero-trust proxy in Go
  • Blocks malicious payloads and sanitizes context windows
  • Implements Merkle Tree audit logs for interaction proof

I scanned 500 domains to test my SPF checker. It found four bugs in the checker.

SPF has a limit almost nobody hits on purpose and plenty of people hit by accident: a receiver is allowed to make ten DNS lookups while evaluating your record, and if the chain needs an eleventh it…

  • Researcher scanned 500 domains with SPF checker, discovered four bugs
  • Checker miscounted DNS lookups, causing false positives/negatives
  • Improper handling of truncated DNS responses led to inaccurate SPF assessment

More from Wednesday 2 September →