In dynalist, this is a user setting called undindent items in-place

- the default behavior of dynalist is similar to the
newlogseq canary - the
unindent items in-placefeature is theoldlogseq 0.0.20 behavior
here’s a gif to show the difference : (old logseq on the left, new canary on the right)

- left (old logseq, unindent in place): it keeps the vertical position but can lead to mixed up categories (
cbecomes a sub-bullet ofb) - right (canary, unindent puts items at the bottom) : bullet vertical order is lost but categories are preserved, maybe better in terms of logic, but with longer lists, that also involves a lot of scrolling
Personnally I prefer the OLD logseq (unindent items in-place), even though it’s less ‘logical’, it’s much faster to use, especially when dealing with long lists of bullets (I always toggled the option in dynalist). I also realize my gif is making it look like the canary version is better, but in a daily workflow I find that keeping the vertical position is much more useful and faster (esp. with long lists) than preserving branch differences.
imo, it should be user-configurable
- about the multiplayer issue : maybe the first person is the
masterand subsequent editors areinvited, the settings is set by themaster? - or maybe multiplayer should lock a block when a user is editing : you can edit multiple blocks as a group, but multiple users can’t edit the same block simultaneously ?