Russia Approves Dedicated Traffic Regulations for Delivery Robots
Russian government agencies have reached agreement on requirements governing how delivery robots move through cities. The new rules will set permitted speeds, define how robots must interact with pedestrians, establish identification procedures, and assign responsibility to operators, according to Minister of Transport Andrey Nikitin.
The draft resolution was developed jointly by the Ministry of Economic Development, the Ministry of Transport, and the Ministry of Internal Affairs. These requirements will first be tested under an experimental legal regime planned to run for three years across 35 regions of Russia.
The document will specify where robots are allowed to operate and which areas will be off-limits. Concrete restrictions and prohibited zones will appear in the final version of the regulation. The central principle states that a rover must not interfere with people or create safety risks on sidewalks.
Authorities will also introduce separate rules for device identification. This measure is expected to help identify the responsible operator if a robot blocks a walkway, collides with a pedestrian, or parks in the middle of a path while carrying a delivery.
The experimental regime is intended to evaluate robot behavior in real urban environments, identify emerging conflicts with pedestrians, and refine restrictions before they are permanently adopted. Over the three-year period, agencies will gather data on practical performance and the effectiveness of the proposed limitations.
Related articles
Yandex Builds Secure KVM Access for BareMetal Servers with IPMI Proxy and Network Isolation
Yandex Cloud engineers developed a layered architecture to grant external users safe KVM access to dedicated BareMetal servers while protecting the shared IPMI network. The solution combines IPMI Proxy containers that normalize vendor-specific protocols into VNC, IPMI Router instances running jool for IPv6-to-IPv4 translation, and strict L2/L3 controls using 802.1X, eBPF, and switch ACLs. DHCP is delivered statelessly by deriving IPv4 addresses from MAC addresses to simplify failover with VRRP. Client-side risks from legacy Java and weak hashes are contained by running minimal containers and mounting ISO images from S3 as external volumes. Continuous permission checks every ten seconds ensure long-lived sessions do not become persistent attack paths. The resulting design unifies access across hardware platforms inside the Yandex Cloud console without exposing BMCs to lateral movement.
WebDesktopGL Framework Turns Web Sites into Desktop Apps on Astra Linux via Chromium
WebDesktopGL is an open-source framework that converts web applications into standalone desktop programs using a local Chromium engine. It was developed specifically for Astra Linux to meet strict licensing requirements that prohibit unlicensed software. The solution supports both X11 and Wayland sessions and has been tested on Ubuntu 24.04 KDE, Ubuntu 22.04 KDE, and Astra Linux 1.8. Key technical components include a modified VirtualGL build for GPU acceleration inside Xephyr or Xvfb virtual displays, custom clipboard synchronization via xclip, and a lightweight xdotool_xseticon utility for window management. Two launch scripts are provided: InfoDoc.sh for full isolation on a virtual X server and InfoDoc_light.sh for simpler direct execution suitable for remote deployment. The project aims to serve as a lightweight, license-compliant alternative to Electron for Linux environments.
DNS Resolver Operator Discovers Missing DNSSEC Validation After Six Months via External Test
A solo developer running VantageDNS, a recursive DNS resolver with filtering, discovered that DNSSEC validation had been disabled for six months after running an external DNS-OARC test. The test flagged "Lookup succeeded while signature was invalid," revealing that the resolver was accepting and returning responses with invalid DNSSEC signatures instead of returning SERVFAIL. Internal monitoring remained green throughout because the absence of validation does not trigger latency spikes, error rates, or availability alerts. The root cause traced back to a comment in the Unbound configuration left from an MVP phase that referenced enabling validation in Sprint 5, which never occurred. After enabling validation using a static trust-anchor-file, the operator documented the correct verification steps using dnssec-failed.org and domains with the AD flag, while noting that performance impact was negligible. The incident highlighted that security properties like DNSSEC validation require active, periodic external probing rather than passive monitoring.
1000 AI Builders Gather for 96-Hour SheNicest Hackathon in Beijing to Build Working Demos
Nearly 1000 creators from technology, product, design, hardware and imaging fields have assembled at the Beijing National Convention Center for the SheNicest 2026 Summer Thousand-Person Hackathon. Over 96 hours participants form teams, iterate rapidly and attempt to convert initial ideas into functional, demonstrable AI products across native applications, agents, intelligent hardware, games and AIGC imagery. A workshop led by Hu Xiaona of 360AI Business Development, HackingClub and AikerWorld examined the transition from individual AI tool use to full organizational adoption. She outlined three progressive stages: tool empowerment, workflow automation and true AI-native organizational redesign. The discussion stressed that simply purchasing AI tools does not change outcomes unless processes, roles and collaboration mechanisms are restructured around human-plus-AI teams. The event concludes with Demo Day on August 30, after which builders must address sales, delivery and sustained value creation.