Eric Myhre

A `p.GetScrollbackWriter() io.Writer` method would be nice and should solve this need. Almost all programs can use a writer like that for the basis of their logging, etc, without needing...

I did something like this before [here](https://github.com/polydawn/go-slog/blob/a8486d66941bc64cae92e32f70f5b52ed0f43b32/slog.go#L89-L91) (in a library that's much less cool than go-prompt)... the only thing I learned is that it's safest to always the cursor back...

We've gone back and forth on how to describe this. It's difficult because what a spec says and what implementations do are also never in perfect alignment, and I think...

It would be really cool to merge this, even if we want to put some disclaimer texts in somewhere. This is way more and better information than we have on...

I tend to say "Multicodec indicator" as a phrase to make this clearer. (Or sometimes even "Multicodec indicator byte", to locally make the emphasis that it's quite short -- nevermind...

I wanna drop a quick note here about a word that @rvagg used in passing during one of our weekly calls, and it stuck in my head and seems like...

I suspect that "indicator" data will be a recurring theme, both in our own designs and in other user applications, so making some standard, reusable, and easily-linkable set of recommendations...

What's the path forward on this? If it's a tractable amount of work / there's time for it, can it be finished soon (i.e. in the next week or two)?...

Ping for if we can make this mergeable.

What happened here? Are these spec changes we should merge as specs, or are they things we should keep in exploration report territory until further ratified and have more implementations?...