I make a post. Someone replies. If it's visible to everyone…
I make a post.
Someone replies.
If it's visible to everyone THEN it becomes a thread.
If it's only visible to a few people it's a group.
Watching Netflix is a watching a stream.
Replies
I like the name Streams for topics more than watching netflix, lol. a stream can be a group or a public channel. any reply can become a new thread and even the potential to be a thread makes it a thread. same input structure gives you multiple options to use it. I see it as an organical organisation of data, kind of... but that's probably just me lol.
!quoted by arghzero
what determines who its visible to?
my point with the post was that it's good to stick to familiar conventions, even if the paradigm is slightly different.
'stream' is a new concept in the context of a chain of messages. most people would associate it with audio of video streaming.
so I set the scope of visibility before or after I make a post, but the UX is different. Clearer labels, better tooltips and better placement of UI
introducing a word like 'stream' is adding unnecessary complexity for new users that have a lot of other new concepts to come to terms with like micro payments and wallet management.
I'm also not sure what the difference is between a stream and a thread and if and when one can become the other.
a stream is like a channel, a room, a folder for threads. they can't become each other.
thanks for clarifying.
why not call it a folder then, it's a concept I know to work like that.
folders are lame :)