Urgent.News

What's breaking now, across thousands of outlets.

Tech

Trump decrees era of 'Super Intelligence' upon us

Federal paperwork to be pulped as agencies told to forget the old name, while critics ask who owns all those .si domains

Trump decrees era of 'Super Intelligence' upon us

President Trump has declared that the era of "Super Intelligence" has arrived, replacing the term "Artificial Intelligence" (AI). In an executive order, he directed the federal government to use the new terminology and reflected the transformative capabilities of these technologies. Trump emphasized that these technologies are not just imitating or automating human intelligence, but are actually amplifying it and unlocking new forms of creativity.

This new era of "Super Intelligence" has the potential to advance scientific and medical research, as well as nearly every other domain of human endeavor. Trump's order directs government agencies to reflect these capabilities and opportunities in all official settings. The change in terminology comes just months after another executive order promoting AI innovation and security in June.

Some speculate that this sudden shift could be linked to investments in .si domains, as noted by a Canadian VC firm. However, without definitive evidence, it is likely that the executive order is a genuine attempt to align government practices with the advancements in AI technology.

Written by urgent.news from The Register's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

This story

This is one outlet's version. Read the fullest account.

Read the original at theregister.com →

More in Tech

Why Your Date Shows 1970: Unix Timestamps in Seconds vs Milliseconds

Why Your Date Shows 1970: Unix Timestamps in Seconds vs Milliseconds You fetch a timestamp from an API, pass it to new Date(), and the screen says January 20, 1970.

  • Unix timestamps count seconds or milliseconds since Jan 1, 1970
  • Mistakes from treating seconds as milliseconds or vice versa
  • Use appropriate unit in code to avoid incorrect dates

3 Redis Design Failures You Should Avoid Before They Become Production Incidents

Caching is usually introduced for one simple reason: Take pressure off the database and make reads faster. The architecture often looks straightforward: Client | v Application | +----> Redis | +---->…

  • Stale data occurs when cached copy becomes outdated, serving incorrect information to users.
  • TTL balances performance and consistency, but doesn't guarantee immediate freshness.
  • Cache invalidation upon database updates prevents staleness but adds complexity.

More from Wednesday 30 September →