Undercutf1 is a terminal-based application providing live Formula 1 timing and driver tracking. It uses a text-based user interface (TUI) for a compact and efficient display of information, including race position, lap times, tyre strategies, and gaps between drivers. A key feature is its variable delay functionality, allowing users to simulate watching the race slightly delayed to avoid spoilers. This open-source project, written in Rust, aims to provide a lightweight and fast alternative to traditional graphical or web-based live timing solutions.
StoryTiming offers a race timing system with integrated video replay. It allows race organizers to easily capture finish line footage, synchronize it with timing data, and generate shareable result videos for participants. These videos show each finisher crossing the line with their time and placing overlaid, enhancing the race experience and providing a personalized memento. The system is designed to be simple to set up and operate, aiming to streamline the timing process for races of various sizes.
HN users generally praised the clean UI and functionality of the race timing app. Several commenters with experience in race timing pointed out the difficulty of getting accurate readings, particularly with RFID, and offered suggestions like using multiple readers and filtering out spurious reads. Some questioned the scalability of the system for larger races. Others appreciated the detailed explanation of the technical challenges and solutions implemented, specifically mentioning the clever use of GPS and the value of the instant replay feature for both participants and organizers. There was also discussion about alternative timing methods and the potential for integrating with existing platforms. A few users expressed interest in using the system for other applications beyond racing.
Summary of Comments ( 39 )
https://news.ycombinator.com/item?id=43734910
HN users generally praised the project for its clean interface, speed, and usefulness for following F1 races without spoilers. Some suggested improvements like adding a relative position indicator instead of just gaps, incorporating qualifying results, and displaying tire strategies. One commenter appreciated the straightforward Python implementation and the use of the
blessedlibrary. Several users also expressed excitement about using it for the upcoming race. The project's ability to introduce an artificial delay for catching up on races was a key feature highlighted positively.The Hacker News post for "Show HN: Undercutf1 – F1 Live Timing TUI with Driver Tracker, Variable Delay" (https://news.ycombinator.com/item?id=43734910) has a modest number of comments, focusing primarily on technical aspects and potential improvements.
One commenter appreciates the project and suggests incorporating a feature to show the fastest lap times for each driver, similar to what the official F1 app offers. They believe this would significantly enhance the utility of the TUI.
Another commenter inquires about the data source used for the project, specifically asking if it's the official F1 API or an alternative source. This highlights the importance of data accuracy and reliability for such applications. The project creator responds, confirming they use the fastf1 library, which pulls data from the official API but caches the results locally for efficiency. They further explain that the TUI doesn't stream live data directly but polls it every 2-3 seconds to update the display.
A different commenter points out that the project appears to require a manual login to the official F1 website to retrieve an access token. They express a desire for a more streamlined authentication process, possibly through an environment variable or command-line argument, to improve the user experience. The project creator acknowledges this as valuable feedback and plans to address it in a future update.
Another user focuses on the technological choices, asking about the use of Textual as the TUI framework. They find it an interesting choice and wonder about the experience of using it. The project author responds positively, praising Textual's ease of use, especially for building interactive elements, while noting some minor quirks they've encountered.
Finally, one comment simply expresses excitement and thanks for the project, appreciating the availability of an F1 timing tool in a TUI format. This highlights the niche this project fills for users who prefer terminal-based interfaces.
In summary, the comments are generally positive and constructive, offering suggestions for improvements while also inquiring about technical details. The discussion revolves around data sources, authentication, the TUI framework used, and desired features, reflecting the interests of the Hacker News audience.