#Protobuf
Mike's Hard Protobuf
November 20, 2026 at 10:00 AM
Protobufチームは Implicit Presence を作ったことを後悔しているらしい
https://zenn.dev/nagatsukey/articles/1782a56f61a45e
Protobufチームは Implicit Presence を作ったことを後悔しているらしい
zenn.dev
November 20, 2026 at 7:06 AM
protoc-gen-gorm (⭐️ 626)

A protobuf compiler plugin designed to generate GORM models and APIs for simple object persistence tasks.

#go
November 21, 2026 at 11:09 AM
📦 xolegator/pinba_extension v1.8.3

Pinba PHP extension: collects request and timer metrics and ships them over UDP (protobuf) to Pinba Engine.

🔗 https://github.com/XOlegator/pinba_extension
November 20, 2026 at 10:12 PM
pbwire_elixir 0.1.18 [updated]

Elixir wrapper over the pbwire NIF: elixir-protobuf structs, C-core wire speed

Licenses: Apache-2.0
November 18, 2026 at 8:30 AM
Friday mood: misread "protobuf gencode" as "protobuf genocide".
November 13, 2026 at 3:11 PM
pbwire 0.1.18 [updated]

Fast Google Protobuf (proto2/proto3) encoder and decoder for Erlang/OTP, implemented as a C NIF. Drop-in replacement for gpb encode_msg/1 and decode_msg/2.

Licenses: Apache-2.0
November 18, 2026 at 8:30 AM
Four bytes, 08 01 10 01, start this litter box. Getting them there meant MD5-signed HTTP requests, MQTT and a stack of protobuf wrappers with CRC-8 frames. A fun teardown of a cloud appliance, from JADX and Frida to Home Assistant. https://master--ytulsiani.netlify.app/blog/furrytails/
Reverse Engineering my cat's litter box
master--ytulsiani.netlify.app
November 21, 2026 at 9:26 AM
pbwire_elixir 0.1.17 [updated]

Elixir wrapper over the pbwire NIF: elixir-protobuf structs, C-core wire speed

Licenses: Apache-2.0
November 16, 2026 at 1:30 AM
📦 jinganix/pbwire v0.1.17

Dynamic protobuf over the pbwire C ABI, schema at runtime, no generated code

🔗 https://github.com/jinganix/pbwire
November 16, 2026 at 1:59 AM
you end up with these sprawling systems that nobody fully understands, built on top of layers of legacy code and duct tape. i keep thinking about that protobuf argument.
November 16, 2026 at 12:54 AM
pbwire 0.1.17 [updated]

Fast Google Protobuf (proto2/proto3) encoder and decoder for Erlang/OTP, implemented as a C NIF. Drop-in replacement for gpb encode_msg/1 and decode_msg/2.

Licenses: Apache-2.0
November 16, 2026 at 1:30 AM
🎲 Testing update:

- php-pecl-protobuf-5.37.0~rc3-1 (PHP 8.2 to 8.6)

github.com/protocolbuff...

⏲️ 12' 📦 120
Releases · protocolbuffers/protobuf
Protocol Buffers - Google's data interchange format - Releases · protocolbuffers/protobuf
github.com
November 13, 2026 at 6:43 AM
📦 hetao29/php-grpc-server-protobuf 1.7.7

The php grpc server framework with protobuf and DO NOT use any 3rd libraries.

🔗 https://github.com/hetao29/php-grpc-server-protobuf
November 12, 2026 at 1:59 PM
💬 @github-actions — PR #5934 : bsync: expose operation creation timestamps
bsync: expose operation creation timestamps by treethought · Pull Request #5934 · bluesky-social/atproto
Commentaire de pull request · PR #5934 bsync: expose operation creation timestamps · @github-actions I found no blocking or non-blocking issues in this PR. What I checked: Proto change is safe for existing clients. created_at = 7 uses a new field number, and google/protobuf/timestamp.proto is already imported in bsync.proto . Clients that don't know about the field will ignore it. @atproto/bsky builds its code from node_modules/@atproto/bsync/proto , so it picks up the field on its next build without needing its own code changes or changeset. The value comes from the database correctly. operation.createdAt is a timestamptz column with a database default, typed GeneratedAlways<Date> . The pg library returns timestamptz values as a Date by default; the only custom parser in db/index.ts is for INT8. So Timestamp.fromDate(...) gets a real Date : ScanOperations already uses selectAll() , so the column is in the result. PutOperation now adds createdAt to its returning clause, and that still happens inside the same transaction as the notify . No migration is needed. The column already exists from 20250527T022203400Z-add-operation . Dependencies and changeset are fine. @bufbuild/protobuf is already a runtime dependency of bsync. bsync is at version 0.1.10 , so a patch changeset fits an additive, non-breaking change before 1.0. Agent files: this doesn't introduce a new pattern, so none need updating. One small note, not a defect: the test assertion expect(op.createdAt?.toDate()).toEqual(expect.any(Date)) would also pass for epoch zero or any wrong date. A bounds check, such as being within a few seconds of the time the test ran, would catch a regression where the timestamp is dropped or set to its default value. Claude review, run Ouvrir sur GitHub →
github.com
November 18, 2026 at 1:15 AM
Changing a Protobuf field and not knowing which services across other repos will break? ProtoMap maps gRPC services, methods, messages and fields across monorepos and multi-repos, then shows blast radius, callers, field-level lineage and dead methods. It serves that context to coding agents...
November 14, 2026 at 4:58 PM
Introducing ProtoSpector: A Burp Suite Extension for Analyzing, Tampering With, and Testing Protobuf and gRPC Traffic https://blog.doyensec.com/2026/11/12/protospector.html
Introducing ProtoSpector: A Burp Suite Extension for Analyzing, Tampering With, and Testing Protobuf and gRPC Traffic
Testing protocol buffers over HTTP can be a notoriously tedious process. Today, we’re excited to announce ProtoSpector, a Burp Suite extension designed to se...
blog.doyensec.com
November 13, 2026 at 8:42 PM
Fixed in this release Bug ID Description 575563262 Updated the Google Cloud client library stack to match Apigee hybrid 1.17 (protobuf 4.x, gRPC 1.82, GAX 2.83, Guava 33.5)
November 12, 2026 at 7:40 PM
Buf wrote protoc-gen-jev: Jev questions defined in Protobuf, typed Go, TypeScript and Python clients out. An experiment, local only, no BSR plugin yet. Buf's Kin Score on APIs.io: 65.3.

https://apis.io/2026/11/10/buf-generates-typed-jev-clients-from-protobuf-and-calls-it-an-experiment/
November 10, 2026 at 9:31 PM
Keeping in mind that the emudhra certificates *probably* will still impact some Internet of Shit devices that will *never* receive updates ...

As I'm poking at this old Barnes & Noble Nook, if I send it a malformed protobuf response, I can cause an android app to crash because it tries to do a […]
Original post on infosec.exchange
infosec.exchange
November 14, 2026 at 3:05 AM