Urgent.News

What's breaking now, across thousands of outlets.

Tech

Russian spacecraft maneuvers in "extreme proximity" to satellite used by Ukraine

Russian spacecraft maneuvers in "extreme proximity" to satellite used by Ukraine

Russian military satellite Kosmos 2612 performed an unauthorized rendezvous with a commercial Earth-imaging satellite operated by the United States, according to orbital intelligence firm LeoLabs. The Russian spacecraft closed the distance from ICEYE-X36, a satellite owned by ICEYE, a Finnish company, at an extremely close range, before maneuvering around the target satellite, remaining nearby for an extended period, and then moving away.

US military officials and independent analysts have been monitoring Kosmos 2612 since its April launch aboard a Soyuz rocket from a spaceport in northern Russia. Within weeks of its launch, it became evident that four out of the six satellites from that launch launch were tracking ICEYE-X36 as they adjusted their orbits to align with the target satellite's orbit.

Written by urgent.news from Ars Technica'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 arstechnica.com →

More in Tech

Why Your Website Is Slow: 7 Performance Problems Developers Should Fix

A website can look beautiful, contain useful content, and offer excellent features, yet still frustrate users if it takes too long to load. Website performance is not just a technical concern.

  • Unoptimized images increase webpage file size
  • Excessive JavaScript slows down website performance
  • Browser caching improves user experience

Why I rate-limit every self-hosted service (and you should too)

I learned this the hard way: an exposed Jellyfin or Vaultwarden instance without rate-limiting is a free buffet for credential stuffing bots.

  • Rate-limit every self-hosted service to prevent attacks
  • Use fail2ban on public-facing services to ban IPs
  • Leverage Nginx and Cloudflare for additional rate-limiting

My local-first photo workflow (Immich + Syncthing + rclone)

After 4 years on Google Photos, I migrated everything to a self-hosted setup that gives me similar features with full data ownership. Here's the stack after 18 months of iteration.

  • Reporter migrated from Google Photos to self-hosted workflow
  • Setup includes Immich, Syncthing, and rclone for photo management
  • Weekly cron job syncs NAS with Backblaze B2 for offsite backup

More from Monday 19 October →