A different mode of operation where it does not alter the root tiddler. The problem right now is that if you want to take notes on a shadow tiddler, or a tiddler from a different source that should not be changed, the action of adding nodes with Streams will change the tiddler by manipulating its stream-list field.
An alternate way of handling the same would be to store the stream-list field for the root tiddler in a separate sidecar config tiddler, for example $:/config/streams/stream-list/
This would also allow for workflows like using Streams to take notes on read-only slides tiddlers, that might have been auto imported or synced from the teacher's tiddlywiki.
One could take this a step further and store relational data for an entire stream in a config tiddler. This might also allow for nodes participating in multiple streams. However, the downside would be that manipulating Streams tiddlers would become a lot more complex.
A different mode of operation where it does not alter the root tiddler. The problem right now is that if you want to take notes on a shadow tiddler, or a tiddler from a different source that should not be changed, the action of adding nodes with Streams will change the tiddler by manipulating its stream-list field.
An alternate way of handling the same would be to store the stream-list field for the root tiddler in a separate sidecar config tiddler, for example $:/config/streams/stream-list/
This would also allow for workflows like using Streams to take notes on read-only slides tiddlers, that might have been auto imported or synced from the teacher's tiddlywiki.
One could take this a step further and store relational data for an entire stream in a config tiddler. This might also allow for nodes participating in multiple streams. However, the downside would be that manipulating Streams tiddlers would become a lot more complex.