",[2910,2911],{"name":2879,"color":2880},{"name":2882,"color":2883},1680,"Tag important for context is removed","2023-02-08T21:56:12Z","https://github.com/elk-zone/elk/issues/1680",0.7880603,{"description":2918,"labels":2919,"number":2926,"owner":2868,"repository":2869,"state":2870,"title":2927,"updated_at":2928,"url":2929,"score":2930},"I have been curiously watching Elk's changes to the status page, from the reordering of replies into threads, the repositioning of mentions to a separate line, the hiding of the mention line when the information is already suggested by surrounding context, to Zen Mode.\r\n\r\nIf we start removing all the boilerplate as this had been the case with these changes, the page actually starts to look like a chat conversation, a list of replies in roughly ordered chronologically, from top to bottom, mostly from old to new, mixing direct replies and sub-conservations, in a single flow.\r\n\r\nElk is not a chat application, but it increasingly looks like one. I feel this shows a willingness to focus on the reading, not only the reading of one status, but of the flow of statuses.\r\n\r\nIt then feels natural to continue to look at chat applications, which, by their nature, enable a more direct form of communication. With this in mind, I've been to trying to see how we could incorporate some simple design patterns from messaging apps into Elk.\r\n\r\n- The action toolbar currently takes the entire width of a post, and acts like an implicit border, a separator between the different posts. I suggest to shorten the action bar, breaking this impression of separation, similar to Slack, Discord, or WhatsApp, where it is often shown aside of the messages in a compact shape.\r\n- The name and handle line is currently shown for all posts, even for statuses that are written by the same individual as part of a thread. I suggest to remove the username line, for the consecutive replies that have the username as the first post, similar to WhatsApp, Discord...\r\n- Replies that start a new thread are only identified by the line \"Replying to\", followed by the name of parent poster. I suggest to add further context to this line, such as the name of the mentions that are part of that initial thread, and an excerpt of the parent message, similar to WhatsApp, Discord...\r\n\r\nI made a quick mock-up to illustrate these changes, the visual aspect will obviously require further work, especially the message preview, but this should sufficient for demonstration purposes.\r\n\r\n\r\n\r\nWith just these few minor changes, replies appear as if they belong to the same document, less segmented, a thread from one individual appears like a longer text, with fewer obstruction, without losing functionality. Messages are seen as part of a context, less likely to be singled out, and picked apart.\r\n\r\nI am curious to hear your opinions.",[2920,2923],{"name":2921,"color":2922},"c: feature","2878FF",{"name":2924,"color":2925},"c: ui","8949BA",1355,"Status design and flow","2023-02-03T05:16:28Z","https://github.com/elk-zone/elk/issues/1355",0.7894048,{"description":2932,"labels":2933,"number":2935,"owner":2868,"repository":2869,"state":2936,"title":2937,"updated_at":2938,"url":2939,"score":2940},"If you boost a post, and your own reply to that post, then your reply should appear inside the original post rather than as a separate boost.\r\n\r\nIt'd look great! That's the only reason really.\r\n\r\n(Kinda like a \"threaded view\", but only for one reply.)",[2934],{"name":2882,"color":2883},2030,"closed","Merge boosted replies into boost","2023-04-29T21:38:36Z","https://github.com/elk-zone/elk/issues/2030",0.75977343,{"description":2942,"labels":2943,"number":2948,"owner":2868,"repository":2869,"state":2936,"title":2949,"updated_at":2950,"url":2951,"score":2952},"UI in Twitter with a line showing the connection between messages\r\n\r\n\r\nAn example from another [mastodon client](https://mas.to/@ayo@fosstodon.org/109341743160486404)\r\n",[2944,2945],{"name":2921,"color":2922},{"name":2946,"color":2947},"p: 1-normal","BFDADC",47,"UI elements to help understand threads","2023-01-30T12:56:53Z","https://github.com/elk-zone/elk/issues/47",0.7612936,{"description":2954,"labels":2955,"number":2960,"owner":2868,"repository":2869,"state":2936,"title":2961,"updated_at":2962,"url":2963,"score":2964},"See: https://elk.zone/m.webtoo.ls/@bencodezen/109626135795293817\r\nIt will only show that post (a reply)\r\nIf you get to it from Notifications or Home, it shows the full thread. Reload and you'll only see the single post.",[2956,2957],{"name":2879,"color":2880},{"name":2958,"color":2959},"p: 2-high","FF4d4d",742,"Direct navigation to post doesn't expand context","2023-01-04T19:55:59Z","https://github.com/elk-zone/elk/issues/742",0.7624139,{"description":2966,"labels":2967,"number":2969,"owner":2868,"repository":2869,"state":2936,"title":2970,"updated_at":2971,"url":2972,"score":2973},"Currently, nearby replies are connected together on the home page, which is great!\r\nIt seems like this doesn't happen on user's profile pages.\r\n\r\nI think we should enable it there as well.\r\n\r\n(For reference: twitter does)",[2968],{"name":2924,"color":2925},637,"Nearby replies on profile pages should be connected","2022-12-29T16:26:39Z","https://github.com/elk-zone/elk/issues/637",0.7657065,["Reactive",2975],{},["Set"],["ShallowReactive",2978],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fbiKf4LHzi9IK-Mb_y57G6v7Mc3CczYYXLiuE5VDscD0":-1},"/elk-zone/elk/593"]