Open wrongu opened 1 year ago
I'm totally supportive and also overwhelmingly unmotivated to write it myself
- we end up wanting to implement our own database
I'd consider this more an analytics and prompt-engineering feature opportunity than a con
- unclear if git fetch/commit/merge loop is fast enough / scalable
LLM roundtrips are the dominant rate-limiter here, not sure that document IO speed really matters in a meaningful way beyond the one or two seconds to put in a "pending" indicator, like you mentioned before
Also there's rate limiting which kinda makes git endpoints a showstopper.
I spent a bit of time in the overleaf source today and wrote some preliminary notes on how it works. My notes document then somehow got erased... so, here's what I can try to piece together again quickly:
'clientTracking.clientUpdated'
packet over the socket, as seen hereAaand that's about as far as I've gotten so far.
Current git-based design
Pros
% @ai: do a thing for me
syntaxCons
Hypothetical direct integration with overleaf
Speculative pros
Speculative cons and things to look into