Ben Rachbach

I'd vote for fully removing, if we do anything. (but probably vote for doing nothing actually)

Another option would be to delete or hide some of the old experiments/trees We could either build that functionality into the app, or it could be a one-time thing that...

Who can see what about which pointers have been opened is sort of a clusterfuck in Mosaic 1 -- it depends on whether you're an admin or not among other...

Depth limit is more important than bandwidth

I think that not having the depth limit enforced has become more confusing now that we've introduced MIB and now that the trees are shorter. See https://ought-inc.slack.com/archives/CMVHEDXAQ/p1569151835045200

We've talked before about doing something like rainbow brackets: https://plugins.jetbrains.com/plugin/10080-rainbow-brackets as @Mati-Roy pointed out, we can't know which bracket is missing or extra -- rainbow brackets are the best tool...

@DerekElkinsOught , such a change would not carry over to Mosaic 2, right?

1. I think it's much better to let participants set preferences, rather than just trying to balance between the roles. 2. Regardless of which way we go, we need to...

(I haven't added more thoughts yet on this issue because I don't think it's a top priority)

@DerekElkinsOught err sorry what I meant was -- are we sharing code between Mosaic 1 and 2 in such a way that implementing this for one would effectively implement it...