Rospotrebnadzor Introduces Age-Based Screen Time Limits for Russian School Students
Rospotrebnadzor has set recommended time limits for Russian school students using computers and interactive boards during classes. The restrictions are designed to protect children's health and depend directly on age, with younger pupils facing stricter caps.
Students in grades 1-2 may spend no more than 20 minutes per lesson at a computer. The limit rises to 25 minutes for grades 3-4, 30 minutes for grades 5-9, and reaches 35 minutes for senior students in grades 10-11, according to RIA Novosti.
Additional rules govern interactive whiteboards. Children under 10 years old should not use them for more than 20 minutes, while pupils over 10 are limited to a maximum of 30 minutes.
Whenever electronic learning tools are employed during lessons or breaks, students must perform eye gymnastics. In classes that rely on traditional paper textbooks, these exercises are recommended only during recess periods.
From 1 September 2026, Russian schools will formally prohibit mobile phones during lessons. Each school will independently determine the policy for smartphone use during breaks.
Related articles
From Root CA to User Authorization in nginx and Apache: Client Certificate Login Explained
This is the third installment in a detailed tutorial series covering the deployment of a two-tier PKI infrastructure with Root CA and intermediate CAs for Person, Server, and Code. The article provides comprehensive configuration guidance for enabling mTLS in nginx and Apache, including full references for all ssl_client_* variables and SSL directives. It explains the differences between password-based and certificate-based authentication, the TLS handshake steps involving CertificateRequest and CertificateVerify, and the importance of proper extendedKeyUsage settings such as clientAuth. Readers learn how to issue client certificates, package them in PKCS#12 format, enforce revocation checks via CRL and OCSP, and safely pass certificate fields to backend applications while mitigating risks from header spoofing. The guide also covers scenarios where the application itself terminates TLS without a reverse proxy and demonstrates login flows protected against CSRF using one-time tokens.
Honeytoken Traps for Detecting Compromised Backends in Encryption Key Services
The article details a honeytoken-based detection system designed to identify when a trusted backend has been compromised and is abusing its signing key to request encryption keys for arbitrary documents. A secret set of fake user and document identifiers is stored only inside the key service using keyed HMAC-SHA256 hashes, ensuring the backend itself cannot discover or bypass the canaries. Any signed request touching these identifiers triggers an alarm, audit logging, and optional emergency lock that wipes master keys from memory. The check is deliberately placed after signature validation but before envelope decryption to avoid false positives from unauthenticated attackers while keeping performance cost low. Two types of canaries address different attack patterns: document canaries catch bulk scraping while user canaries detect forged grants for non-existent principals. The mechanism has been deployed in production, with live tests confirming silent failure responses externally and clear canary_trip plus emergency_lock events internally. Limitations include inability to catch targeted extraction of a single real user’s documents and the fact that detection occurs after a canary key has already been issued.
Yisaqi Automation Magician Delivers Self-Healing RPA to Fix Low ROI in Enterprise AI Agents
Meituan's internal experiment revealed that widespread AI agent adoption drove daily token costs into the millions while introducing errors into business processes. MIT research confirmed that 95 percent of generative AI pilots fail to deliver measurable returns despite tens of billions in spending. Yisaqi's Automation Magician addresses these gaps by extending the agent lifecycle beyond conversation to include exploration, automated testing, self-healing, and export of stable scripts. The platform uses natural language input to generate resilient automation flows that adapt to UI changes without repeated model calls. Deployments at Jiage Food and a major central SOE financial shared service center demonstrate large-scale coverage of tax, finance, and manufacturing processes with minimal manual intervention. Zhongtian Technology reported 80 percent efficiency gains and annual savings exceeding one million yuan after rolling out the solution across 112 scenarios.
Aeroflot to Accept Digital Rubles for Ticket Purchases Starting September 2026
From September 1 2026 Aeroflot will begin accepting digital rubles as a payment method for airline tickets both on its website and in company sales offices. Customers choosing the new option online will see a QR code generated by the site that must be scanned in a participating bank application. The payment is then confirmed from the digital wallet hosted on the Bank of Russia platform and an electronic ticket plus receipt are issued automatically. The same QR-based flow will be used at physical ticket counters where the code appears on the terminal. Ordinary bank cards and other payment methods remain fully available and no physical digital cash is required. On the same date MTS will start accepting digital rubles through MTS Pay while Rostelecom and Megafon are also preparing their systems. Russian authorities have clarified that the digital ruble is the third official form of the national currency alongside cash and non-cash funds rather than a cryptocurrency.