Stories with Tag Protobuf

• Show HN: Zero-codegen, no-compile TypeScript type inference from Protobufs

  permalink

  Posted: 2025-04-14 15:41:03

  Verbose tl;dr

  protobuf-ts-types is a tool that automatically generates TypeScript types from Protobuf schemas without requiring any code generation or compilation steps. It leverages the Protobuf runtime library to infer types directly, offering a simpler and faster workflow for TypeScript developers working with Protobuf. This eliminates the need for separate code generation tools and keeps the TypeScript types synchronized with the Protobuf schemas, reducing potential errors. The project aims to improve developer experience and efficiency when using Protobuf in TypeScript projects.

  The Hacker News post titled "Show HN: Zero-codegen, no-compile TypeScript type inference from Protobufs" introduces protobuf-ts-types, a new TypeScript library that dynamically generates TypeScript types directly from Protobuf (Protocol Buffer) schemas without requiring a separate code generation step or compilation process. This approach deviates from the traditional method of using protoc and plugins to generate static TypeScript code from .proto files.

  The core functionality revolves around parsing Protobuf schema files (.proto) at runtime, using the @protobuf-ts/runtime library. This parser understands the structure and data types defined within the Protobuf schema. From this parsed schema, protobuf-ts-types dynamically constructs corresponding TypeScript types, mirroring the Protobuf definitions. This includes complex types like nested messages, enums, and various scalar types. These generated types can then be used directly within a TypeScript project, enabling type-safe interaction with Protobuf data.

  The elimination of the code generation step simplifies the development workflow. Developers no longer need to configure and run protoc with specific plugins, nor manage the generated TypeScript code. Changes to the Protobuf schema are immediately reflected in the TypeScript types without recompilation. This facilitates rapid prototyping and iterative development with Protobufs.

  The library aims to provide comprehensive type mapping, accurately representing the nuances of Protobuf schemas in the TypeScript type system. It also supports advanced features like custom Protobuf options and well-known types. The runtime approach taken by protobuf-ts-types positions it as a flexible and efficient solution for integrating Protobufs into TypeScript projects, particularly those that benefit from a streamlined development process and dynamic type generation. The project is open-source and available on GitHub.

  • TypeScript
  • Protocol Buffers
  • Protobuf
  • Type Inference
  • Zero-Codegen
  • No-Compile
  • Code Generation
  • data serialization
  • Web Development
  • javascript
  • Static Typing
  • developer tools

  Summary of Comments ( 13 )
  https://news.ycombinator.com/item?id=43682547

  Verbose tl;dr

  Hacker News users generally expressed interest in the project, praising its approach to Protobuf type generation in TypeScript. Several commenters highlighted the advantages of avoiding code generation and runtime dependencies, contrasting it favorably with existing solutions like protoc and protobufjs. Some questioned the handling of specific Protobuf features like oneof and any, and discussions arose around potential performance implications and the project's compatibility with existing JavaScript Protobuf libraries. The author actively engaged with commenters, clarifying design choices and addressing technical questions about the project's inner workings. Overall, the reception was positive, with many seeing the project as a promising alternative for TypeScript Protobuf integration.

  The Hacker News post titled "Show HN: Zero-codegen, no-compile TypeScript type inference from Protobufs" (https://news.ycombinator.com/item?id=43682547) sparked a discussion with several interesting comments.

  Many commenters expressed appreciation for the project's approach of avoiding code generation, which simplifies workflows and reduces potential maintenance overhead. One commenter highlighted the elegance of using generics for this purpose, contrasting it with the often cumbersome code generation processes they've encountered.

  Several users brought up comparisons to other Protobuf tooling within the TypeScript ecosystem. ts-proto was mentioned frequently, with some users highlighting perceived advantages and disadvantages of each project. The discussion touched upon performance characteristics, the level of type safety offered, and the developer experience in terms of setup and usage. One user specifically asked about the differences between the presented project and ts-proto regarding how they handle optional fields and oneofs, indicating a desire to understand the nuances of each approach.

  One commenter inquired about the handling of nested messages and the generation of appropriate TypeScript types, which led to a brief discussion about the library's capabilities in this area. Another user raised the important point of how protobuf-ts-types manages breaking changes introduced by modifications to the .proto files, a crucial aspect for maintaining type safety in evolving projects.

  The topic of runtime type checking was also raised. While the project focuses on static type safety during development, one commenter questioned whether runtime validation against the inferred types is also performed, which could add an extra layer of robustness in production environments.

  Overall, the comments section reflects a generally positive reception of the project, with users expressing interest in its unique approach and engaging in productive discussions comparing its features to existing solutions. The discussion also highlights key considerations for Protobuf tooling in TypeScript, including handling optional fields, oneofs, nested messages, breaking changes, and potential runtime type checking.

• Block YouTube ads on AppleTV by decrypting and stripping ads from Profobuf (2022)

  permalink

  Posted: 2025-03-18 07:59:50

  Verbose tl;dr

  This blog post details a method for blocking YouTube ads on Apple TV by intercepting and manipulating encrypted traffic using pfSense, a firewall and router platform. The author leverages pfSense's ability to decrypt TLS/SSL traffic, then uses a custom Python script to parse and filter Google's Protocol Buffer (protobuf) messages, removing the components associated with advertisements before re-encrypting and forwarding the modified traffic to the Apple TV. This approach eliminates ads without relying on DNS blocking or other methods that YouTube might easily circumvent. The post provides a detailed explanation of the setup process, including installing necessary packages, configuring pfSense, and implementing the Python script.

  This blog post by Eric Draken details a complex method for blocking YouTube advertisements on Apple TV by intercepting, decrypting, and modifying the network traffic responsible for delivering those ads. The core issue stems from YouTube serving ads within the same protocol buffer (protobuf) stream as the video content itself, making simple blocking based on URL or domain insufficient.

  Draken's approach leverages pfSense, an open-source firewall and router distribution, as the primary tool for manipulating this traffic. The process begins with configuring pfSense to act as a transparent proxy, effectively intercepting all network traffic flowing to and from the Apple TV. This interception allows pfSense to analyze the data passing through.

  Since YouTube utilizes HTTPS, the encrypted traffic must be decrypted to analyze the protobuf messages. This decryption is achieved through a man-in-the-middle (MITM) attack, where pfSense intercepts the SSL/TLS handshake and presents its own certificate to the Apple TV, effectively posing as the YouTube server. To facilitate this, the root certificate authority (CA) generated by pfSense needs to be trusted by the Apple TV. Draken explains the process of generating and installing this certificate.

  Once decrypted, the traffic, specifically the protobuf messages containing the video stream and embedded ads, is accessible. Draken utilizes a Python script executed by pfSense, leveraging the python-protobuf library. This script parses the intercepted protobuf data, identifies messages pertaining to advertisements, and effectively removes or "strips" these messages from the stream before forwarding the modified, ad-free stream to the Apple TV.

  The blog post provides detailed instructions on setting up the necessary pfSense components, including the installation of required packages, configuration of the transparent proxy, and setup of the SSL/TLS interception. It also includes the Python script responsible for protobuf manipulation, meticulously explaining the logic behind identifying and removing the ad-related messages. The post highlights the complexity involved in decoding and manipulating protobufs, demonstrating how different protobuf definitions are required based on factors like video resolution and other stream parameters. Furthermore, Draken addresses the maintenance aspect of this method, acknowledging the need to update the protobuf definitions and Python script as YouTube evolves its ad delivery mechanisms. He suggests strategies for maintaining effectiveness, such as monitoring logs for errors and adapting the script to changes in YouTube's protobuf structure.

  • YouTube
  • ad blocking
  • AppleTV
  • pfSense
  • Decryption
  • Protobuf
  • Proxy Server
  • TLS Interception
  • network security
  • Ad Removal
  • 2022

  Summary of Comments ( 385 )
  https://news.ycombinator.com/item?id=43396735

  Verbose tl;dr

  Hacker News commenters generally express skepticism about the effectiveness and practicality of the described method for blocking YouTube ads on Apple TV. Some doubt the claim that all YouTube ads are served via protobuf, suggesting the method is likely to break frequently. Others point out the resource intensiveness of decrypting and re-encrypting TLS traffic on less powerful hardware like the Apple TV. Several commenters propose alternative ad-blocking solutions like Pi-hole or NextDNS, arguing these are simpler and more robust. The privacy implications of MITMing TLS traffic are also raised. While some acknowledge the cleverness of the approach, the consensus leans towards it being more of a proof-of-concept than a practical, long-term solution.

  The Hacker News post discussing the blog post about blocking YouTube ads on AppleTV by decrypting and stripping ads from Protobuf has a moderate number of comments, sparking a discussion around the effectiveness, ethics, and technical aspects of the approach.

  Several commenters express skepticism about the longevity of this method. They predict that Google will likely adapt and change its ad delivery system, rendering this specific decryption technique obsolete. This cat-and-mouse game between ad blockers and ad providers is a recurring theme. Some even suggest that Google might intentionally introduce breaking changes to specifically target this method, while others take a more neutral stance, viewing it as an inevitable evolution in the arms race between ad blockers and platforms.

  The legality and ethical implications of bypassing ads are also debated. While some argue it's within the user's right to control their viewing experience, others point out that YouTube's terms of service likely prohibit such manipulation. This leads to a discussion about the broader issue of ad-supported content and the balance between user experience and content creator compensation.

  Technical details of the implementation are discussed, with some questioning the efficiency and potential side effects of decrypting and re-encrypting the stream in real-time, particularly on less powerful devices like the AppleTV. The use of Protobuf for ad delivery is also mentioned, with some commenters expressing surprise or noting its prevalence in Google's infrastructure.

  Alternative ad-blocking methods are suggested, including Pi-hole and other DNS-based solutions, which some commenters consider more robust and less prone to being circumvented. There's also a mention of using a custom DNS setup to block known ad servers.

  Finally, some users share their personal experiences with ad blocking and express frustration with the increasing prevalence of ads on streaming platforms. This sentiment fuels the discussion about the ongoing struggle between users seeking an ad-free experience and platforms relying on advertising revenue.