"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 Ajdyna

@Emil Ajdyna https://github.com/Linen-dev/linen.dev/issues/596 see the feature change log here. We can upload the gifs and images here and a description of how it works. I'm still thinking about how to showcase features.

@Emil Ajdyna I made the drag and drop more subtle to 95% it feels cleaner

@Emil Ajdyna https://github.com/Linen-dev/linen.dev/issues/581 let's prioritize this one tomorrow. One of our users brought it up

@Emil Ajdyna 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.

@Emil Ajdyna Created this issue https://github.com/Linen-dev/linen.dev/issues/620 for attachments.

We should be able to keep track of which conversations were read and unread Questions: What is the behavior for unread? I'm leaning towards having the cursor scrolled up to where they left off similar to Slack Scope: Limit this to non feed view for the first version Potential solution: 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.

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

Have you had a look at https://github.com/widgetbot-io/embed yet? I reckon there's some useful prior art there.

Hi btw! ☺️ Had a great chat with kam yesterday.

I'm looking forward to talking more about chat design in the coming days/weeks. A lot of my thinking on the subject is summed up in this product announcement I did, plus the article it links to.

hey, this is zach

Hello everyone, I just found you guys on Hackers News (https://news.ycombinator.com/item?id=35718417). It would be great if the entire team can vote UP on it... Or even if you can put a small pop-up for all new users to get an even bigger reach.

Btw for new users coming in from HN feel free to checkout our github repo as well https://github.com/linen-dev/linen.dev

would love to help out on this if needed! will tinker with getting dev env setup this weekend. would be nice to have that process more thoroughly documented...is there a way to bypass sentry usage?

@linen/web:dev

requires a valid dsn D: apologies if the answer is obvious, i just spent a few minutes tinkering with it tonight that's it... great looking stuff... really excited to see where this goes and congrats on the hn placement