securitylab_nJuly 13, 2026🇷🇺Translated from Russian

Study Reveals That Names Gradually Shape Adult Facial Appearance Through Societal Expectations, Not Genetics Alone

A person's name, chosen by parents at birth, can gradually influence not only their character and behavior but also their physical appearance, according to a new study that combined human experiments with machine learning analysis.

The research began with a straightforward experiment in which volunteers were shown photographs of strangers and asked to select the correct name from several options. Both adults and children participated as subjects in the photo sets.

Participants in both groups guessed the names of adults from their facial photographs at rates noticeably higher than chance. In contrast, photographs of children produced no such pattern: neither adult nor child volunteers could reliably identify a child's correct name based solely on appearance. The authors suggest that newborns and young children have not yet developed the facial traits that society commonly associates with specific names.

To validate the results through an independent method, the team employed a machine learning system. The algorithm compared faces of individuals sharing the same names and measured degrees of similarity. Analysis revealed that adult Michaels, Alexanders, or Annies tended to resemble one another more closely than people with different names, while no comparable effect appeared among children.

Researchers next tested whether natural age-related facial changes could explain the findings. They used digital techniques to artificially age childhood photographs, generating images that approximated how the same individuals might look as adults.

If appearance were determined purely by genetics and maturation, participants should have guessed names from these aged images with success rates similar to those achieved with real adult photographs. However, this expectation was not met. After artificial aging, the children's faces did not align more closely with their actual names, and the machine learning algorithm likewise detected no increased similarity among same-named individuals.

All results converge on a single conclusion: people are not born with faces that match their names. Instead, changes accumulate gradually during maturation under the influence of social expectations.

Psychologists have long discussed the phenomenon known as social structuring. The concept holds that society continuously attaches labels, expectations, and stereotypes to individuals. Over time these associations begin to shape habits, communication style, facial expressions, posture, and other behavioral traits.

The effect can be understood as a classic self-fulfilling prophecy. People around an individual named Nikita, for example, may unconsciously anticipate certain behaviors, and the person repeatedly encounters the same societal reactions, eventually adjusting to meet those expectations—sometimes even internalizing them.

The influence of social expectations extends well beyond names. If such a relatively weak factor can leave visible traces on a person's face, far stronger effects are likely produced by gender, cultural background, ethnicity, and other enduring social markers that accompany individuals throughout life.

Related articles

HabrOther

OAuth Authorization Server Built Without Storing User Profiles

The article details the evolution of an OAuth Authorization Server that deliberately avoids storing user profiles, relying instead on external identity providers for authentication. It addresses three core constraints: hundreds of dynamically created isolated APIs, a public SPA client without a BFF, and the inability of resources to query the AS on every request. The design separates concerns so the AS handles only clients, tenants, grants, audiences, scopes, keys, sessions, and token issuance while the Main API owns profiles and roles. Tokens are managed securely inside a Service Worker using a custom FedCM grant, eliminating races across tabs and reducing XSS exposure. The approach minimizes blast radius, simplifies compliance, and keeps the AS replaceable without affecting product domain logic.

HabrOther

Why a 202-Character License Key Uses ECDSA P-256 Instead of Ed25519 or RSA

A developer building offline license verification for a .NET desktop application evaluated Ed25519, RSA, and ECDSA P-256 before selecting the last option. The decision was driven by the requirement for zero external dependencies, keys short enough for manual entry from email, and support for key rotation without breaking existing licenses. Although Ed25519 offers faster verification and a smaller public key, it is absent from System.Security.Cryptography in both .NET 8 and .NET 10, with API approval only targeted for version 11. RSA-2048 produces signatures too long for practical use, resulting in a 571-character Base32 string that users would find cumbersome. ECDSA P-256 with SHA-256 delivers a fixed 64-byte signature that becomes a manageable 202-character key when encoded in Base32, while remaining fully available in the runtime. The article also covers performance measurements, the risks of ECDSA nonce generation, and the deliberate choice of the IEEE P1363 signature format to guarantee fixed-length output.

HabrOther

Pilcrow Publishes Free Comprehensive Guide on Web Authentication

Author Pilcrow has released a detailed, ad-free handbook covering authentication and authorization practices for web applications. The resource draws on personal experience and includes practical examples in JavaScript and Go. It examines password-based methods, email verification, multi-factor authentication, passwordless flows, and passkeys while highlighting associated risks and usability trade-offs. The book also provides in-depth guidance on session management, token security, expiration policies, and email address handling as account identifiers. Recommendations emphasize choosing methods that match application security requirements and user expectations. Additional context is given on OWASP resources and community support channels.

HabrOther

redb 3.4.0 Adds Replay Checkpoints, Shared Runtime Layer and Declarative Secrets Handling for .NET Ecosystem

redb 3.4.0 delivers operational improvements for the .NET integration platform that includes typed storage over Postgres, MSSQL and SQLite, the redb.Route engine modeled after Apache Camel, the Tsak runtime with dashboard and clustering, and redb.Identity for OIDC and OAuth 2.1. The release focuses on post-deployment resilience with replay checkpoints that capture message state at named points inside routes, allowing safe re-execution of downstream steps without duplicating side effects. A shared runtime layer moves framework assemblies into a separate Libs/shared directory so that individual DLLs can be replaced without rebuilding or redeploying the entire Tsak or Identity packages. Secrets are now declared with a [Sensitive] attribute on endpoint options, ensuring URIs containing passwords or keys are sanitized before they reach logs, metrics or health checks. Additional controls include role-based access to management APIs, persistent audit trails and cryptographic signing of dynamically loaded modules. All Pro features remain free on the entire 3.x line with no licensing server required.