You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We could skip running indexers for folx running cabal headlessly purely as a backup/sync node, which would make sync faster (no cpu fighting over sync vs indexing) and lower draw on cpu/io.
The text was updated successfully, but these errors were encountered:
More like a 'multifeed pinning bot', since it'd need to support N cores and whatever sync protocol cabal ends up using. In the deeper future, if we go the pubsub route, it'll also need awareness of that too. Maybe by default it'd just hold subscriptions to all public channels, for example.
Much much shorter term, this is just skipping the core.use(...) code that sets up the views.
We could skip running indexers for folx running cabal headlessly purely as a backup/sync node, which would make sync faster (no cpu fighting over sync vs indexing) and lower draw on cpu/io.
The text was updated successfully, but these errors were encountered: