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

🪐 Building @neynar, join us in /neynar

Only on restart, 3M messages but can be configured via cli option

That’s a great idea. 
- How often does a hub do the “am I behind?” check?
- How many is too many behind?

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

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

Hi folks, the snapshot is really awesome and fast but for me it downloaded the snapshot and then restarts the downloading of snapshots again. Looking closely at the logs I see an error message but it’s all \n so thinking there’s a typo or bug

I am now regretting the upgrade.
Getting the following error

The snapshot is really life saver, was having hard time to have my hub fully synced previous but from version 1.11.1 onwards the sync is a breeze 👍 

222 $DEGEN

Incredible upgrade! Syncing 80M messages only took 3 hours. Amazing!👍