Urgent.News

What's breaking now, across thousands of outlets.

Tech

Mittal hits back after Musk cries foul over Starlink

Bharti Airtel chairman Sunil Bharti Mittal rebutted Elon Musk's claims that Starlink's satellite internet service is being obstructed in India, asserting that his own venture, Eutelsat OneWeb, is currently awaiting regulatory approvals. On Wednesday, Musk accused undisclosed oligarchs of blocking Starlink in India to preserve their dominant position, without naming any specific entities.

The telecom market in India comprises three private players: Reliance Jio, Bharti Airtel, and Vodafone Idea. Starlink, Jio Satcom, and Eutelsat OneWeb are the three satellite communications companies vying to launch services in the country. The Indian government has issued licenses to these three entities for commencing operations, but all require spectrum and security clearance.

Bharti Mittal commented on Musk's allegations at the India Mobile Congress, stating that his venture is awaiting its own approvals. Bharti Group-backed Eutelsat OneWeb and Jio Satcom were the first two satellite communication companies to receive licenses, but they too are yet to secure spectrum and security clearance for service deployment.

Jio Platforms' Managing Director, Akash Ambani, declined to comment on the matter. The government expressed dissatisfaction with Musk's allegations, emphasizing the need for licensees to comply with security norms as part of a fair and non-discriminatory authorization process. The ministry stated that all three licensees are currently at the same regulatory stage, and suggesting the framework or its application is unfair or discriminatory is baseless and misconceived.

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

Read the original at economictimes.indiatimes.com →

More in Tech

One build, every environment: runtime configuration for micro frontends

Look at your pipeline. If it builds staging and production separately from the same commit, you are shipping an artifact nobody tested. You tested the staging one.

  • Implement runtime configuration to avoid separate builds for each environment in micro frontends.
  • Application fetches environment-specific values as a small JSON document at startup.
  • This approach reduces build waste, potential failures, and enables quick rollbacks.

How to Ship Canary Releases for Microfrontends Without Losing Your Mind

TL;DR: Canary releases let you test new microfrontend versions on a slice of your traffic before going full rollout. Most teams build custom tooling for this. You don't have to.

  • Canary releases allow gradual rollout of new microfrontend versions to a small user percentage.
  • Challenges include complex traffic routing, invisible versioning, and instant rollback requirements.

Module Federation with Vite in production: what changes

Module Federation started in Webpack, and for years that is where it stayed. It works on Vite now, through @module-federation/vite , and works well — but Vite's dev server and Vite's build are two…

  • Module Federation integrated with Vite's development server and build process
  • Dependency deduplication differs between development and production builds
  • Shared dependencies should be marked deliberately to avoid conflicts

Migration Diary: Port the Tool Contract Before a Free Server Inherits Paid Endpoints

You should port the tool contract before you repoint a coding workflow at free model access. Leftover paid endpoints, unbounded retries, and vendor tool names survive cancellation and keep steering…

  • Port the tool contract before switching to a free server.
  • Create a portable contract and leftover scan for rehearsal.
  • Use a decision table to classify bindings for migration.

More from Thursday 8 October →