Content
@
0 reply
0 recast
2 reactions
Carlos Matallín
@matallo.eth
This is seriously cool and the kind of technology that makes you excited to build stuff with it https://github.com/electric-sql/pglite
4 replies
0 recast
32 reactions
Greg
@greg
I’ve had this starred for a couple months waiting on an idea to use it for! What initially comes to mind for you?
3 replies
0 recast
10 reactions
Stephan
@stephancill
would love to hook it up to the lazy indexer and run opencast fully client side
1 reply
0 recast
3 reactions
Greg
@greg
actually now that you say it, i think i found this repo right before farcon when i was telling you about the maximally decentralized local client idea! would be sick
1 reply
0 recast
3 reactions
Stephan
@stephancill
the lazy indexer's footprint is < 4gb for a single user's network, so totally doable imo
3 replies
0 recast
2 reactions
Greg
@greg
that is all casts by users that i follow for example? 4gb seems high
1 reply
0 recast
0 reaction
Stephan
@stephancill
it's a complete backfill for the users you follow. mine ends up around 2.5gb iirc, don't imagine it getting much bigger than that so 4gb is conservative haven't actually looked into the composition of that data, it's possible there could be a mistake somewhere. local first can also probably do some optimizations like lazily fetching casts >7 days old
1 reply
0 recast
1 reaction
Greg
@greg
yea realistically you can just fetch the latest page of 1000 items (still high) for each data type to have a solid reverse chrono feed
0 reply
0 recast
1 reaction
