hubs

We've released 1.11.1. @wazzymandias.eth made it so that hubs will now automatically use snapshot sync to catch up if they are too many messages behind. 

Note that this will reset the db, if you're running a replicator you can disable this to be safe, by setting `CATCHUP_SYNC_WITH_SNAPSHOT=false` in your .env file

Folks really love the pace of the team -  it just wondering if you’re thinking of doing like an LTS type of hub versioning

🗽based; 

building skeet.build 🟠;
building @buoy 🛟; 
building check.supply 🏦;

We’re not mature enough yet for an LTS style release. Maybe eventually when the protocol is more ossified.

Ok thanks - just afraid of taking a hub down during upgrades. We rely on the grpc streams

Farcaster

Hubble Replicator v2 

We have a proposal for a new design to tackle the problems with the existing replicator. If you run a replicator today, we'd love to get your feedback on this. 

https://warpcast.notion.site/Replicator-v2-Public-6562ad1e6eef4c4ab2c27cf82aa759c1

Yeah, we run multiple hubs internally and there’s significant complexity dealing with this. We’re thinking about the problem, and might do something like an aggregator/load balancer to help. No eta though.

See

Yeah, we run multiple hubs internally and there’s significant complexity dealing with this. We’re thinking about the problem, and might do something like an aggregator/load balancer to help. No eta though.

See https://warpcast.com/v/0x05d9e809