implement ui for threaded messages?

[cblgh]

if we'd really want to support the same kind of functionality that e.g. slack does we could look at implementing threads.

i think this could actually work pretty well if we expose the key of each message when we get them in cabal-node's getMessages() function

[hackergrrl]

Nice! Thoughts from my hacking on OSM + hyper{db,core}:

• key@seq makes for a good unique message identifier. There isn't a great API for it yet in hyperdb, but it IS possible to, given a hyperdb node you can get the feed key (+ convert to/from hex) and the node's sequence number. Again, it's a bit awkward in hyperdb, but multifeed exposes the raw hypercores, making this very simple.
• SSB does threads by having a property on each threaded msg called root that contains the key of the message it branches off of. Having this property for threaded msgs would make it easy for clients that can't support threaded msgs easily (e.g. IRC bridge) ignore them or display them in some other way.

[hackergrrl]

+1 if this gets implemented in core (cabal-db?) and clients just "interpret" the message data

[okdistribute]

yeah I like that idea @noffle !

And multifeed looks awesome

[callil]

I always dreamed of the ability to use the root of a thread to quickly generate a new channel in things like slack. I wonder if cabal could use that to loft the thread into a channel keeping the history intact.

[simbolo]

I think we need to start thinking of another sidebar to implement something like this. Uhm, I'm gonna try working on a couple mockups for this if anyone else is ok with that.

[cblgh]

"I always dreamed of the ability to use the root of a thread to quickly generate a new channel in things like slack. I wonder if cabal could use that to loft the thread into a channel keeping the history intact."

ohh yes, that would be very interesting!

On Tue, 14 Aug 2018 at 23:43, Callil Capuozzo notifications@github.com wrote:

I always dreamed of the ability to use the root of a thread to quickly generate a new channel in things like slack. I wonder if cabal could use that to loft the thread into a channel keeping the history intact.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/cabal-club/cabal-desktop/issues/3#issuecomment-413026055, or mute the thread https://github.com/notifications/unsubscribe-auth/ADrvWpe5tJbv8nm0jjlcqEINTAmlGRDCks5uQ0RogaJpZM4UMhg7 .

[todrobbins]

Friends, do we want to revive this discussion/work?