Hacker News new | ask | show | jobs
by afarra 4382 days ago
We debated over this, we want to group multiple together (waiting a bit before sending the update to see if any others come in), but people love the "instant feedback" of the update coming right away.

What we plan to do is have the first update come instantly, but then any subsequent ones would get grouped together. That way you still get the instant feedback 90% of the time but at the same time you don't get flooded if someone decides to do a lot of changes in a short time.

1 comments

Ah. Seems reasonable. You could probably tweak the timing (updates no more often than every X minutes) and volume (no more than Y changes per update) dynamically with things like an exponential backoff (to some limit) to optimize engagement over time.

The ideal knob settings may change depending on whether people are trying to collaborate synchronously or asynchronously. BTW, are you currently doing diff-match-patch to account for multiple editors?