From 4 items, 2 important content pieces were selected
Technology News
- Audacity 4.0 Released with Qt6-Based UI Rewrite ⭐️ 8.0/10
- .name Third-Level Registrations Face Termination ⭐️ 7.0/10
Technology News
Audacity 4.0 Released with Qt6-Based UI Rewrite ⭐️ 8.0/10
Audacity 4.0.0, a major release of the open-source audio editor, is now available from its GitHub releases page, headlined by a Qt6-based UI rewrite. The release matters because Audacity remains one of the most widely used open-source audio tools, and this version marks a significant interface modernization. Community attention is high, with users sharing a release video and a developer interview about the new UI. Specific changelog details were not included in the item, so exact fixes and compatibility constraints are not confirmed.
hackernews · ClydeN · Sep 3, 10:53 · Discussion
「Background」 Audacity is a long-standing open-source audio editor, and version 4.0 marks a major rewrite of its user interface by migrating from the wxWidgets toolkit to Qt6, reusing the framework from Muse Group's MuseScore Studio 4. The release also adds Windows ASIO support and legacy project imports, while retaining backward compatibility with earlier Audacity files. This UI overhaul follows years of community concern about Muse Group's stewardship, including past telemetry controversies and forks such as Tenacity and Sneedacity.
「Community discussion」 Commenters shared a release video and a developer interview by Muse's Head of Software, and reactions were mixed: one user found the 4 beta cleaner and said it fixed long-standing issues, while another said JACK/Pipewire integration problems remain unaddressed. Others raised lingering concerns about audio.com integration and asked what happened to post-telemetry forks like Tenacity and Sneedacity.
References
Tags: #audacity, #open-source, #audio-editing, #qt6, #release
.name Third-Level Registrations Face Termination ⭐️ 7.0/10
A proposal would terminate third-level .name domain registrations, affecting existing owners of x.y.name domains and releasing the corresponding y.name second-level domains. The .name TLD itself is not being terminated, and owners of second-level domains are not directly affected. Critics argue that existing registrations should be honored or that released second-level domains should be reserved to prevent squatting, and the plan raises broader DNS security and governance concerns. The proposal's specific timeline and implementation details are not specified in the available material.
hackernews · pavel_lishin · Sep 3, 14:54 · Discussion
「Background」 The .name top-level domain was approved by ICANN in 2000 and is operated by VeriSign; unlike most gTLDs, it allowed registrations at the third level (for example, x.y.name) and offered personalized email forwarding. In May 2026, VeriSign proposed discontinuing those third-level registrations and the email service, and on 28 July 2026 ICANN approved the plan, under which existing third-level registrations would be unilaterally terminated so the corresponding second-level domains could be released for new registration.
「Impact」 Existing owners of third-level .name domains would lose their registrations, and the released second-level domains could become vulnerable to squatting.
「Community Discussion」 Commenters largely agree that terminating existing third-level registrations is unfair, with some suggesting that current registrations should be grandfathered and released second-level domains reserved. One commenter clarified that .name itself is not ending, while others questioned the TLD's cookie and security model and called for decentralized alternatives.
Tags: #domain names, #DNS, #ICANN, #web infrastructure, #internet policy