Signal Goes Password-Free, Julia Gets Faster, and AMD Closes the CUDA Gap

Signal announced that phone-number-free account registration will be implemented using zero-knowledge proofs — a cryptographic protocol that allows the platform to verify a registration is legitimate without learning anything about who is registering. The move addresses a core tension in Signal's design: phone numbers provide effective resistance to Sybil attacks, where bad actors create thousands of fake accounts, because they cost real money and tie to real-world identity, but they also create privacy and accessibility barriers. Zero-knowledge registration opens Signal to users in countries where purchasing a SIM card requires government ID, people escaping abusive situations who cannot safely be traced through a phone number, and journalists and activists operating in adversarial environments. The 141-comment Hacker News thread included working cryptographers discussing the specific ZK scheme Signal appears to be deploying, and commenters noted that the architecture may also offer a more defensible technical position relative to identity-verification frameworks being proposed by regulators in the UK, EU, and elsewhere — though whether regulators will accept ZK proofs as satisfying those requirements remains an open question.

Julia 1.13 was released, generating 239 upvotes and positive discussion from the language's technically engaged Hacker News community. The headline improvements target compilation latency — the 'time to first plot' problem that has historically made Julia frustrating for interactive use despite strong runtime performance — and threading and parallelism primitives that strengthen its case for large-scale scientific computing workloads. Julia has occupied a specific competitive position for roughly three years: demonstrably faster than Python for numerical computing at runtime, but hampered by startup latency and a smaller general-purpose library ecosystem. The 1.13 release continues a consistent pattern of closing those gaps without sacrificing the performance characteristics that differentiate the language, presenting the large scientific Python community with a more credible migration argument than it has faced previously.

A project enabling CUDA code to run on AMD GPUs through the HIP translation toolchain — specifically targeting Windows, which has been a weak point for AMD's CUDA compatibility even as ROCm has progressed on Linux — drew 169 upvotes and 92 comments. Experienced commenters offered a useful calibration: compatibility is not equivalence. Applications using standard compute primitives translate reasonably well; applications relying on NVIDIA-specific optimizations or memory access patterns tuned to NVIDIA hardware will see degraded performance or failures. The practical value, commenters noted, is for organizations that cannot obtain NVIDIA allocation — still a genuine constraint as of September 2026 — and need to run a meaningful subset of workloads on AMD hardware rather than at full NVIDIA-equivalent speed.

Also noted in the GPU discussion: HP's ZGX Fury is now orderable, featuring NVIDIA's GB300 Superchip with 748 gigabytes of unified memory on a single system. For context, memory constraints are among the primary limits on what model sizes are currently practical for inference deployment; a system with that memory footprint materially raises the ceiling on model size for edge and on-premises use cases, at a price point expected to give enterprise procurement teams pause.

EterDB, a Postgres fork designed specifically for incident recovery, appeared as a Show HN post with 40 upvotes and 19 comments. The project integrates point-in-time recovery, automated incident detection, and recovery workflow orchestration directly into the database rather than relying on external tooling. The comment thread raised sharp questions from experienced database engineers about WAL management, recovery time objectives, and whether the problem is genuinely database-layer or is better addressed through Postgres with properly configured backup infrastructure — a discussion that functions, in effect, as a rigorous public product evaluation.