i think there is some mis-conception between building on farcaster (the protocol) vs. building on warpcast APIs ... currently the Merkle team offers Wrapcast APIs (which farcaster-{py,js} wraps around) providing developer access to Merkle's "twitter clone" that does not actually run on hubs
hubs are launching soon (i think next week?) and it looks they need help here https://github.com/farcasterxyz/hubble/issues/497 to actually enable a broader development ecosystem building on top of the farcaster "protocol"
hubs are launching soon (i think next week?) and it looks they need help here https://github.com/farcasterxyz/hubble/issues/497 to actually enable a broader developers ecosystem which will build on top of the farcaster "protocol"
I don’t see any reason farcaster-py will not be supporting a Hubble implementation, I think js is already set up to. Will definitely be involved in the python discussion for my own usage. Also making the easiest implementation of Hubble. I don’t know that requiring new devs to use it is the best situation though