Not currently possible that I know of, if you're using Chrome's multiple-users functionality. I daresay you could make it work if you were to use two instances of Chrome with different user-data directories, as described here: http://www.wikihow.com/Create-Multiple-Google-Chrome-Profiles

Supporting multiple sidebars in an open (fully customizeable) way is somewhere on the Sidewise todo list.

Not currently possible that I know of, if you're using Chrome's multiple-users functionality. I daresay you could make it work if you were to use two instances of Chrome with different user-data directories, as described here: http://www.wikihow.com/Create-Multiple-Google-Chrome-Profiles

Support multiple sidebars in an open (fully customizeable) way is somewhere on the Sidewise todo list.

Thanks for catching that! Fixed, and released as version 2013.4.18.1.

My apologies for the delay on fixing this. This should now be working properly in version 2013.4.18.0.

Apologies to all for the delay on fixing this. This should now be working properly in version 2013.4.18.0.

If anyone's still seeing this problem please post.

I've released a fix for this in version 2013.4.18.0. If you want it right away, go to your Extensions page, check "Developer mode" then click "Update extensions now".

Apologies for the delay.

The code to handle this has been released in version 2013.4.18.0.

---

Oh that's bad. Good find :D The cause turns out to be the favicons shown in the sidebar -- if one of them is from a "malware site", we get the malware warning page in the sidebar too.

I've created a kludgy-but-functional mechanism to detect and correct this problem and it should be in the next release. 

The solution isn't pretty but it works. Basically, when Sidewise notices that the malware page is showing in the sidebar, it will ask the user if they want to fix the problem.

Sidewise then loads all the tree's favicons into a new "testing" tab. If that tab comes up with the malware-page, then we know that one of those favicons is causing the problem. Now we split the list of favicons in half and test each half separately in the same way, to figure out which half contains the bad favicon. We continue this process by repeatedly subdividing the "contains the malware favicon" list in half, then again testing each half ... until through the process of elimination we narrow the list down to a single favicon that causes the malware warning.

At that point, we have identified the offending favicon, and replace it in the tree with the default Chrome favicon. Fixed!

The code to handle this has been released in version 2013.4.18.0.