Shane da Silva

Closing as the question was answered. Thanks!

Closing as the question was answered. PRs welcome!

Closing as fixed. Let us know if you're still seeing this issue after upgrading to Hubble 1.12.2. Thanks!

Sorry for the delay in response. If you're still seeing this after upgrading to Hubble 1.12.2, and are using an instance with 30+GB of RAM and 200+GB of storage, let...

#1994 was released in Hubble 1.12.2. Please open a new issue if you're still seeing issues (though bear in mind the issue might be purely on the Warpcast side, not...

Thanks for following up! Closing this as you answered your own question. `ReactionRemove` messages must be kept so that hubs that received the corresponding `ReactionAdd` will consider the reaction removed.

The network is growing quite rapidly. 200GB is likely going to be the minimum size in the near future. Hubs right now require ~150GB. Long term we have other ideas...

Implemented in #1948. For those reading this issue, keep the following in mind (originally posted [here](https://github.com/farcasterxyz/hub-monorepo/pull/1948/#issuecomment-2157273596)): >the `HEALTHCHECK` directive **does not** cause Docker to auto-restart containers that fail healthchecks. All...

Thanks @mscurtescu, sorry for the delay in response. One point of clarification: the `HEALTHCHECK` directive **does not** cause Docker to auto-restart containers that fail healthchecks. All it does is update...

I don't think we should trust `X-Forwarded-For` by default (allows an attacker to avoid rate limiting by spoofing a different IP each time) but agree a configurable option to trust...