You are reading content from Scuttlebutt
@Anders %xwGw5P1lKBMuTag480tg/gzVhjIkLCYLDRXRWSGDsEU=.sha256
Re: %ApqSTV4Jm

@punkmonk there are some uint32 limits in jitdb mainly because they are smaller in size so the indexes are smaller. But there is also some grow functionality, so it might not be too hard to add some logic to automatically convert to uint64 once it reaches a certain size. If you are interested in taking this on I'd be happy to help.

User has chosen not to be hosted publicly
@Anders %OTT/8Yam3WHXkmeRxf/s5VwYH9DSA35NNKZb/vHzq4g=.sha256

@punkmonk exactly. Also see this. I would try putting in 4GB into async-append-only-log first and from there try to use it in jitdb.

Join Scuttlebutt now