"I think we should render messages in the thread separately (even if they are from the same user) and add a possibility for the user to merge them together (just like threads).
Right now it is unclear when the user posted the message.
The count in the channel and what you see on the right in the thread is also very confusing." - @emil
@emil I think I prefer the old way of drag and drop where you can see the card move. I feel like it is easier for someone to understand how it works. I can see how this as a UX it might be easier to tell what is being dragged in to but I don't think we should re invent a new visual language.
We should be able to keep track of which conversations were read and unread
What is the behavior for unread? I'm leaning towards having the cursor scrolled up to where they left off similar to Slack
Limit this to non feed view for the first version
Since we are using cursor based pagination we should be able to to keep track of when someone as closed the page or exited.
We could use the Elixir push service to keep track of the status of when someone is online and maybe where on the page they are. The moment they close the browser the status would change and we can send an event to backend api and store the latest time stamp of when the user has left the page or where on the page they are.
Linen desktop client
11/17/2022, 2:13 PM
We're currently working on a desktop client, written in tauri. One of benefits of tauri is that the final size of the client should be very small, given it utilizes a native web renderer.
We are still figuring it out and you can expect some refactors here and there, however we're hoping to have an alpha version available soon. You can track the progress here https://github.com/Linen-dev/linen.dev/tree/main/apps/desktop