Farcaster Devs

When I  ask people who build tools using the gRPC hub interface, and they all manually pull/copy the protobuf definitions from the monorepo. There is no programatic way to check if you are using the latest .proto files or if they changed since the last time you used them, or what changed.

Ideally, they would be a separate repo, with their own version. Maybe there are other, better solutions. But can we do something about it? 

cc @sanjay

I suppose a good way would be versioning the proto as a separate repo maybe, unsupported hub operations from a client to a server in grpc/proto usually returns the default value for a field, and in the reverse way receiving an unknown response from a server with more recent proto definitions puts them in an "unknown" section iirc. I think in theory you can even include artifacts from compiled protos that resemble versioned information? Descriptor set files?

Dad, geek, conversation liquidity provider. vrypan.net (home), /weatherxm (work), @l--o--l (fun). Also https://paragraph.xyz/@purplesubmarine

For me, proto versioning would be great. A proto "package" would help too (a farcaster-proto-1.13.zip file for example, that changes only if there is a change, not just following the Hubble versions).

And a separate repo would help because I can check and see that there was a new commit, what changed and probably why (vs going through irrelevant monorepo commits).

I suppose a good way would be versioning the proto as a separate repo maybe, unsupported hub operations from a client to a server in grpc/proto usually returns the default value for a field, and in the reverse way receiving an unknown response from a server with more recent proto definitions puts them in an "unknown" section iirc. I think in theory you can even include artifacts from compiled protos that resemble versioned information? Descriptor set files? https://protobuf.com/docs/descriptors

I make lights blink and play with crypto (cryptography and cryptocurrency) at /neynar. they/them or he/him

I need to know if I should rebuild my farcaster-py library, and provide devs who use it with a way to know that the version they are using or will use supports X but not Y (for example does not yet support profile location data). How will reflection help?