Russian Neighbors Fined Over 200,000 Rubles for Defamatory Remarks in Apartment Building Chat as Supreme Court Upholds Ruling
Two participants in a shared apartment building chat have been ordered to pay more than 200,000 rubles in compensation after Russian courts, including the Supreme Court, upheld a ruling that their messages about a neighbor were defamatory.
The dispute originated from complaints about noisy tenants in one apartment. Residents raised the issue with the property owner in the building chat, after which the conversation descended into personal attacks. The residents also contacted police, but officers found no grounds for administrative action against the owner. The owner then filed a civil claim for protection of honor and dignity, submitting the chat logs, SMS messages, and recordings of telephone conversations as evidence.
A court-appointed linguistic expert concluded that some of the public statements did not contain swear words or formal insults yet included derogatory descriptions and suggestions of mental health issues. The court ruled that these remarks could not be treated as permissible evaluative opinions. Obscene language was identified in private conversations. Complaints to the police were not considered abusive, as the court found no evidence that the residents had misused their right to contact state authorities.
One defendant was ordered to pay more than 100,000 rubles and the second a slightly lower amount. When calculating the compensation, the court noted that the plaintiff had also behaved inappropriately during the conflict, but this did not exempt the defendants from liability. The decision survived review at every higher instance, including the Supreme Court.
The ruling signals that messages posted in a building chat are treated as public statements capable of damaging an identifiable person's reputation, even without explicit profanity.
Related articles
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.
Why 99% Attack Detection Rules Generate 99.9% False Positives in Real SOC Environments
A detection rule claiming 99% attack coverage with only 1% false positive rate sounds effective on paper, yet in practice it produces roughly one thousand false alerts for every genuine incident. Using a realistic example of 200,000 daily logins containing just two real compromises, the article demonstrates that 1.98 true positives are buried among 2,000 false positives. Bayes' theorem explains why sensitivity improvements barely move the needle while reducing the false-positive rate or narrowing the population yields dramatic gains in precision. The piece outlines three practical levers—lowering FPR, scoping rules to high-risk accounts, and cascading cheap-then-expensive checks—that cut analyst workload by orders of magnitude without sacrificing meaningful coverage. It also warns that chronically low-precision rules train analysts to ignore alerts, eventually leading to the rule being disabled despite remaining in compliance matrices. The recommended metric pair is therefore confirmed detections alongside coverage, rather than coverage alone.