Thread by @Conaw

Alright friends - hate to be the bearer of bad news, but turns out that one of the larger sources of problems with our new synchronization system seems to be how it interacts with @roamhacker's Roam42 extension.

If you're having any sync or performance issues - try removing that

We're going to try to get to the heart of the bug, and hope to have an update soon that will fix -- so you can use both Roam42 and the updated sync system (which otherwise is much faster)

First we're working on a url that will let you fall back to old sync if u need Roam42 more

The good news is - as far as I can tell, this is only a problem on multiplayer graphs where you have collaborators editing at the same time as you.

And we have not yet rolled the new sync system to the book club -- so very few folks seem to be affected by this bug

Full details

To be extremely extremely clear

1. This issue probably didn't affect you
2. If it did, was in no way @roamhacker's fault.
3. Next tweet will have instructions that will let you try old sync system - so you don't have to give up on your roam/js modifications

Stopgap solution

About half of the roamgraphs are on a new sync system which in most cases seems to be faster and more reliable.

If you want to try it out -- add

?uselink2=true

to the end of your url (check for updates first)

If you're seeing new bugs, try

uselink2=false