Urgent.News

What's breaking now, across thousands of outlets.

Tech

Satya Nadella says "we welcome" the "deliberate pacing needed to get alignment right", and announces a "Code of Conduct" for Microsoft's MAI models (Satya Nadella/@satyanadella)

Any pursuit of superintelligence has to be grounded in the core principle that if the AI we build is not helping humanity and under human control, it's not worth pursuing. We also need to accelerate and spread the benefits of AI, such that they are diffused broadly across countries, communities, a...

We haven't written up this one. Techmeme has the full story — the link below goes straight to it.

Read the original at x.com →

More in Tech

The Contagion of Fear

  • Students spread panic by warning of computer virus
  • AI expert Jacob Coxon claims 10% AI killing humans risk
  • Fear of AI driven by experts' speculation over reality

Do you know how Chinese super apps work? A study with Flutter

Você já deve ter ouvido que "o WeChat é seu WhatsApp, seu banco e seu Uber, tudo no mesmo app". Essa comparação vende bem a ideia pra quem nunca usou um super app chinês, mas é só a superfície.

  • Chinese super apps have three-layer architecture: shell, runtime, and mini-programs
  • Shell handles authentication, payments, system permissions
  • Runtime executes third-party code for mini-programs in isolated, secure manner

At the edge, the number that matters is memory - not throughput (specially in Ramageddon)

We rebuilt LF Edge eKuiper in Rust and ran it against eKuiper, Telegraf and Redpanda Connect on five real MQTT workloads — one core, 1 GB of memory, and output checked message-by-message.

  • Memory usage, not throughput, is key metric in resource-constrained environments
  • Rekuiper, Rust-based engine, maintained memory usage between 5 and 10 MB
  • Design choices include bounded queues, incremental window aggregation, offline sink cache

API Rate Limiting: What Actually Breaks When You Get It Wrong

Most teams add rate limiting to their API as an afterthought — usually right after something has already gone wrong. A scraper hammers an endpoint, a client integration goes into a retry loop, or a…

  • Simply setting a single request limit is insufficient as all requests don't have equal costs.
  • Centralize rate limit counters across multiple instances to prevent overloading the system.

More from Sunday 13 September →