I think this is getting closer but still not quite where we want it.

By only looking at the message, Lib.getState() calls that use the same message but increment counters now don't appear in the behavior logs after the first iteration.

e.g. https://github.com/webrecorder/custom-behaviors/blob/main/behaviors/timeline.js#L54

Do we actually need to be checking for dupes at all? Almost seems like we're creating an undocumented barrier in the way of developing custom behaviors.

Yeah, you're right, maybe we should just remove this. I think was mostly used for autoscroll to reduce logging, but that should just be handled in Autoscroll..

Updated to 0.9.2 for behavior webrecorder/browsertrix-behaviors#104 fix