Universe Proves Ordinary After All: High-Profile DESI Study Claiming Giant Aligned Cosmic Structures Collapses Following Data Correction
A high-profile paper published in the journal Nature that claimed to detect giant, directionally aligned filaments in the cosmic web has been effectively invalidated after independent researchers identified fundamental errors in the data analysis.
The original study examined observations from the Dark Energy Spectroscopic Instrument (DESI), which has produced one of the largest three-dimensional maps of the universe to date. The dataset included 47 million galaxies and quasars covering more than 11 billion years of cosmic history within the 13.8-billion-year lifespan of the universe.
According to the authors, the filaments of the cosmic web appeared significantly longer than predicted by existing models and, more strikingly, showed a preferred orientation rather than random alignment. Such a finding would have challenged the cosmological principle, the foundational assumption that the universe is statistically homogeneous and isotropic on sufficiently large scales, with no preferred directions.
An independent cosmologist who re-examined the work discovered that the team had used luminosity distance instead of the conventional comoving distance when measuring large-scale structure. These two distance measures serve different purposes and are not interchangeable for studies of cosmic-web geometry. In addition, the analysis did not incorporate the fact that distances between distant objects change over time due to the ongoing expansion of the universe.
After substituting the correct distance metric and applying the necessary expansion correction, the apparent giant aligned structures disappeared. The revised results showed a cosmic web that remains inhomogeneous on moderate scales but exhibits no mysterious preferred direction, fully consistent with the cosmological principle.
One of the original authors has disputed the critique, arguing that the re-analysis focused on the distribution of structures rather than their orientation. The independent reviewer maintains that the identified errors affect both types of measurements and are independent of the chosen analytical approach.
The controversy has raised broader questions about the peer-review process at leading journals. Although Nature typically requires papers to present results capable of significantly advancing a field, reviewers cannot realistically verify every line of code or calculation. The authors of the disputed study also bypassed the common practice of posting a preprint on the arXiv server, depriving the community of an opportunity for early scrutiny. Scientific embargoes imposed by journals further limited pre-publication discussion, highlighting ongoing tensions between the desire for high-impact announcements and the need for thorough, open verification.
Related articles
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.
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.
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.
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.