ICANN is transitioning from the WHOIS protocol to the Registration Data Access Protocol (RDAP) for accessing domain name registration data. RDAP offers improved access control, internationalized data, and a structured, extensible format, addressing many of WHOIS's limitations. While gTLD registry operators were required to implement RDAP by 2019, ICANN's focus now shifts to encouraging its broader adoption and eventual replacement of WHOIS. Although no firm date is set for WHOIS's complete shutdown, ICANN aims to cease supporting the protocol once RDAP usage reaches sufficient levels, signaling a significant shift in how domain registration information is accessed.
The popular Material Theme extension for Visual Studio Code has been removed from the marketplace due to unresolved trademark issues with Google concerning the "Material Design" name. The developers were requested by Google to rename the theme and all related assets, but after attempting to comply, they encountered further complications. Unable to reach a satisfactory agreement, they've decided to unpublish the extension for the time being. Existing users with the theme already installed will retain it, but it will no longer receive updates or be available for new installs through the marketplace. The developers are still exploring options for the theme's future, including potentially republishing under a different name.
Hacker News users discuss the removal of the popular Material Theme extension from the VS Code marketplace, speculating on the reasons. Several suspect the developer's frustration with Microsoft's handling of extension updates and their increasingly strict review process. Some suggest the theme's complexity and reliance on numerous dependencies might have contributed to difficulties adhering to new guidelines. Others express disappointment at the removal, praising the theme's aesthetics and customizability, while a few propose alternative themes. The lack of official communication from the developer leaves much of the situation unclear, but the consensus seems to be that the increasingly stringent marketplace rules likely played a role. A few comments also mention potential copyright issues related to bundled icon fonts.
Taner Şener, the creator of FFmpegKit, a commercial wrapper around FFmpeg for mobile development, announced that he's ceasing development and support. Due to complexities in maintaining FFmpeg across various architectures and operating systems, increasing maintenance burden, and inadequate revenue to justify continued development, he's chosen to shut down. Existing clients can continue using their purchased licenses, but future updates and support are discontinued. The core issue is the difficulty of sustainably supporting a complex project like FFmpegKit, even as a paid product, given the rapid pace of mobile development and the substantial engineering effort required for compatibility. While acknowledging the disappointment this will cause some users, Şener emphasizes the unsustainable nature of the project's current trajectory and thanks users for their support over the years.
Hacker News users discuss the author's decision to discontinue FFmpegKit, an iOS/Android FFmpeg library. Several commenters express disappointment, highlighting FFmpegKit's ease of use compared to alternatives like MobileFFmpeg. Some suggest the decision stems from the difficulty of maintaining cross-platform compatibility and the complex build process involved with FFmpeg. Others speculate about the author's motivation, including burnout or lack of financial viability. A few offer alternative solutions or express hope for a successor project. The lack of clear documentation for building FFmpeg directly is also a recurring concern, reinforcing the value of projects like FFmpegKit.
Summary of Comments ( 273 )
https://news.ycombinator.com/item?id=43384069
Hacker News commenters largely express frustration and skepticism about the transition from WHOIS to RDAP. They see RDAP as more complex and less accessible than WHOIS, hindering security research and anti-abuse efforts. Several commenters point out the lack of a unified, easy-to-use RDAP client, making bulk queries difficult and requiring users to navigate different authentication mechanisms for each registrar. The perceived lack of improvement over WHOIS and the added complexity lead some to believe the transition is driven by GDPR compliance rather than actual user benefit. Some also express concern about potential information access restrictions and the impact on legitimate uses of WHOIS data.
The Hacker News post "Launching RDAP; sunsetting WHOIS" discussing ICANN's plan to replace WHOIS with RDAP has generated a moderate amount of discussion, with a focus on the practical implications and perceived shortcomings of the transition.
Several commenters express skepticism about RDAP's purported benefits, particularly regarding data accessibility. One user highlights the increased complexity of querying RDAP compared to WHOIS, noting the requirement for specific queries for each top-level domain (TLD) and the varied responses that can make parsing difficult. This complexity is contrasted with the simplicity of WHOIS, which offered a single point of access. The user expresses doubt that RDAP will be as widely adopted or as useful as WHOIS.
Building on this theme, another commenter points out the lack of a comprehensive, unified RDAP interface, leading to fragmentation and increased difficulty in obtaining domain information. They argue that this lack of a centralized system negates the benefits of a structured data format, making RDAP less practical than WHOIS for many users. They lament the potential loss of a useful tool and the added complexity introduced by RDAP.
Another commenter questions the actual improvements offered by RDAP, highlighting the potential for similar abuse and privacy issues despite the structured data format. They point to the existing challenges with WHOIS data accuracy and the possibility of similar inaccuracies persisting in RDAP.
One user expresses concern about the impact on security researchers and incident responders who rely on WHOIS data. They note the ease of automating WHOIS lookups and worry that the distributed nature of RDAP will hinder efficient data gathering for security purposes.
The discussion also touches upon the internationalization aspects of RDAP, with one user praising the support for internationalized domain names and other languages. However, another commenter questions the enforcement of accuracy in internationalized data, suggesting that this aspect might introduce further complexities.
Finally, a couple of comments reflect a more accepting stance towards the transition. One user simply acknowledges the change, while another points out the limited utility of WHOIS even before its deprecation, hinting at the potential for RDAP to offer improvements, albeit with challenges.
In summary, the comments on Hacker News largely express concerns about the practical usability and effectiveness of RDAP as a replacement for WHOIS. The primary themes include increased complexity, lack of a unified interface, potential for similar data accuracy issues, and the impact on security researchers. While some acknowledge the potential benefits of structured data and internationalization, the prevailing sentiment appears to be one of skepticism and apprehension regarding the transition.