\r\n\r\n\u003Cimg src=\"https://user-images.githubusercontent.com/4262489/209167825-b8de6750-e51c-4126-8f7c-91d439462b26.png\" width=\"250\" />",[2942,2943,2946],{"name":2891,"color":2892},{"name":2944,"color":2945},"s: on hold","A03F0B",{"name":2921,"color":2922},516,"Hide the Explore tab if trends are disabled for the instance","2023-02-04T21:37:04Z","https://github.com/elk-zone/elk/issues/516",0.7666784,{"description":2953,"labels":2954,"number":2956,"owner":2871,"repository":2872,"state":2873,"title":2957,"updated_at":2958,"url":2959,"score":2960},"As a user I want to filter my timeline to only show me content that is currently relevant to me.\r\n\r\nI would like to gain a better UX by having a filter icon e.g. in the top left corner right to the profile icon while being in the Home timeline\r\nWhen I click on that icon, a list with checkboxes will be shown to me where I can deselect some content\r\nBy default all \"filters\" are applied, so I can just deselect on demand\r\n\r\nFor the initial draft, I think this doesn't need to get persisted somewhere\r\n\r\nFilters could be e.g.:\r\n- post by bot\r\n- post contains sensitive\r\n- post is a repost\r\n- post is from a mutual\r\n- post is from a tag I follow\r\n\r\nSo by default everything is active, and when I deselect \"post by bot\", all post that where posted by a bot are just filtered out\r\n\r\nThis should be only a simple filter feature targeted for non-higher filter usages like using lists or e.g. #1540\r\nThe filter also will just be applied client side\r\n\r\nIt could be discussed if the filter should be swapped from everything is checked by default to \"hide X\" and then needs to be checked\r\nlike:\r\n- hide posts by bot\r\n- hide sensitive posts\r\n- hide reposts\r\n- hide mutual posts (this is unlikely 🤔)\r\n- hide tagged posts (this is also unlucky 🤔)\r\n\r\nAs we can see, maybe the \"hide\" does not so much sense, and it is more like I want to deselect everything down to: \"show me only from mutuals and tags\" or something like that\r\n\r\nThis feature does NOT aim for higher filters like \"tag contains X\" or \"boost count is higher then y\" but instead should just be a quick accessible filter",[2955],{"name":2868,"color":2869},1931,"Filter for Home timeline","2023-04-01T13:48:39Z","https://github.com/elk-zone/elk/issues/1931",0.77076435,{"description":2962,"labels":2963,"number":2965,"owner":2871,"repository":2872,"state":2873,"title":2966,"updated_at":2967,"url":2968,"score":2969},"Hello, I would like to propose that:\r\n\r\n- One feed remains chronological, as it is now.\r\n- The other feed would be \"Smart\" and also display entries chronologically, but only show entries that we haven't seen yet. This means that if we have viewed a certain number of entries and then closed the app, when we reopen the Smart feed, it will display only the entries that we haven't seen yet.",[2964],{"name":2891,"color":2892},2883,"Smart feed — It only shows unread entries","2024-06-14T05:05:27Z","https://github.com/elk-zone/elk/issues/2883",0.77602583,{"description":2971,"labels":2972,"number":2975,"owner":2871,"repository":2872,"state":2873,"title":2976,"updated_at":2977,"url":2978,"score":2979},"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.",[2973,2974],{"name":2891,"color":2892},{"name":2932,"color":2933},1355,"Status design and flow","2023-02-03T05:16:28Z","https://github.com/elk-zone/elk/issues/1355",0.77746207,["Reactive",2981],{},["Set"],["ShallowReactive",2984],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$ftzMm_0-youUI1p8FLPc7jCStJZGkYH8-e8eMSDXMhAM":-1},"/elk-zone/elk/1070"]