That's an interesting UseCase, @mario -along w/ some interesting content, 
including talk by Don Blair <https://www.youtube.com/watch?v=uog2ByDcJ2c> 
(NB: that farm in Portugal he talks about is mine :-).  

Wish i'd had access to such toolchain during all those COVID-year Zoom 
conferences i attended, proceedings of which are mostly lost in time "like 
tears in the rain"

In a standalone-scenario like this, where the wiki serves sole purpose of 
conference record, with just one tiddler for the conference, serving as 
"parent" to all those subtiddlers that it has spawned, then:  yes: no need 
to "flatten" the stream; that would actually defeat the purpose - purpose 
being to summarize and/or elaborate on the "live" content. 

The challenge i see with this is all the manual node-wrangling involved 
-greatly facilitated by "Streams" affordance for outlining via keyboard 
shortcuts (esp w/ shortcut "cheatsheet" in the sidebar, as you suggest), 
but to whatever extent that process could be further automated, i see that 
as a real opportunity, especially w/r/t the work of correlating these nodes 
with actual video timecodes.  Your system correlated the node tiddlers to 
your own clock-time, it appears... But then when video from Zoom (Skype, 
whatever) gets cut up and pushed out to separate YouTube videos, as it. has 
done in this case, then what is the optimal workflow? 

I guess what i might do to refine this to my prefs is have each talk in the 
conference with its own "parent" tiddler;  then if i could zero-out that 
timeline of which you speak at start of each talk, it should then track 
pretty close to the final video, so long as they don't edit-out any 
portions of it in post-production.  To achieve perfect alignment, presuming 
a continuous stream, you might need to tweak these codes after -which would 
involve a bulk renaming of all related tiddlers i guess. Am just thinking 
out loud here, w/ benefit of hindsight...

Anyway, as it stands: this looks to me like a very good solution to that 
problem in the majority of YouTube videos published, whereby most of them 
have either no "shownotes" at all, or else notes that serve some 
promotional purpose(s) that most viewers would MUCH rather see complemented 
(if not entirely replaced) with a helpful time-coded set of jump-links to 
whatever section(s) of content they consider to be of interest.
To that end, Mario, this represents a solid step forward. Thanks for 
sharing it here!

/walt



On Thursday, June 24, 2021 at 10:01:12 PM UTC+1 PMario wrote:

> Hi Walt,
>
> I don't use streams regularly but from time to time it's convenient for 
> brainstorming and refactoring to get ideas sorted. 
>
> I did a heavy test with an early version in August 2020 for 2 days, where 
> I did follow an online conference about DAT (now Hyper). It was possible to 
> follow the live-stream and the chat to keep notes in real time. The wiki 
> can be seen at: http://dat-conf-2020.tiddlyspot.com/ ... BUT it doesn't 
> make sense on it's own. You'll need the Agenda 
> <https://events.dat.foundation/2020/schedule/> and the Videos 
> <https://events.dat.foundation/2020/stream/> . 
>
> I did set streams up in way, that tiddler titles create an automatic 
> "timeline" ... Which will allow my to connect the notes to the videos, if 
> needed. 
>
> Every tiddler has this format DAT-CON/2020/07/30/16:08:49-582 
> <http://dat-conf-2020.tiddlyspot.com/#DAT-CON%2F2020%2F07%2F30%2F16%3A08%3A49-582>
>   
> DAT-CON/<year>/<month>/<day>/0hh:0mm:0ss-XXX
>
> So the TW tree-macro can also be used to view the timeline 
> <http://dat-conf-2020.tiddlyspot.com/#test-tree-macro> in a different 
> format. The tree-macro in the example only shows the tiddler titles. To 
> show more info I needed to modify the macro according to my needs, but 
> that's not public. 
>
> I basically use the notes with the default search function. .. I open the 
> tiddlers .. have a look for my own keywords to find the tiddler with the 
> exact "timestamp"... With the timestamp I can find the related discussion 
> or presentation in the Videos. ---> That's the main purpose of this 
> outline. 
>
> The published version doesn't contain any personal notes. ... So for me 
> there is absolutely no desire to "flatten" the structure. ... I "widen" it 
> with my notes and additional links to loosely related blog posts and 
> github repos ... 
>
> My initial feedback can be found here: 
> https://groups.google.com/g/tiddlywiki/c/1jTwdmq8cgI/m/Orm9JRVNBQAJ ... 
> The main problems that I did mention there with streams V0.1.10 are fixed 
> with the latest version (0.2.18) of streams. So I'm perfectly fine with the 
> possibilities it offers. 
>
> For my personal convenience I need to adjust 1 little bit of CSS 
> <http://dat-conf-2020.tiddlyspot.com/#CSS>. I need a different colour for 
> the "collapse indicator", if a parent node is collapsed. It would be cool, 
> if this was configurable, but in normal cases I only copy paste the CSS 
> tiddler. 
>
> I need to add the "keyboard shortcut 
> <https://saqimtiaz.github.io/streams/#%24%3A%2Fplugins%2Fsq%2Fstreams%2Finfo%2Fkeyboard-shortcuts>"
>  
> cheat-sheet to the right sidebar by adding the tag $:/tags/Sidebar. @Saq 
> This could be part of the control-panel config options ;) I need it for the 
> shortcuts that I use seldom. 
>
> For me "streams" is probably _the_ "easiest to use" "realtime" outliner 
> I've ever used. 
>
> For exporting you should probably have a closer look at the filters 
> <https://saqimtiaz.github.io/streams/#Streams%200.2%20improvements%2FFilters> 
> that Saq mentioned. Especially the last one. ... 
>
> You are right, there is some room for improvement if "lists of stream 
> tiddler titles" are shown. They are not very informative ... But imo the 
> problem is, the needed list templates are highly use-case specific. .. So I 
> actually don't know how they should look like. Not even form my own 
> usecases. 
>
> Since stream uses a field named "parent" to link to parent tiddlers my tocP 
> macro <https://wikilabs.github.io/editions/tocP/> can also be used to 
> show the structure. BUT in the current form this isn't too useful, since it 
> only shows the title. ... I was experimenting to show the "subtitle" field, 
> but adding that field manually is way too much work, to be done in 
> realtime. (Mainly because finding good tiddler sub-titles is hard) ... I'm 
> still not sure, how to solve this in a convenient and fast way. 
>
> I hope this helps. 
>
> have fun!
> mario
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/d7a5d72e-4c52-411a-913a-91c5d2939b50n%40googlegroups.com.

Reply via email to