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

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

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?

The library wouldn't have protobufs in it at all. It would fetch them all with reflection at runtime 

Lots of clients support reflection. You lose lots of the niceties of typing though. 

Most common use of reflection I've used it with grpcurl. 

One rust example:

Lots of clients support reflection. You lose lots of the niceties of typing though. 

Most common use of reflection I've used it with grpcurl. 

One rust example: https://docs.rs/protobuf/latest/protobuf/reflect/index.html

This is not how it works in most cases. If you use Go, Rust, Python, etc, you have to compile .proto files to generate stubs. And you need to understand the logic a method implements, in order to provide an interface to devs using your library.