\r\n\r\n\u003Cimg src=\"https://user-images.githubusercontent.com/4262489/209167825-b8de6750-e51c-4126-8f7c-91d439462b26.png\" width=\"250\" />",[2007,2010,2013],{"name":2008,"color":2009},"c: feature","2878FF",{"name":2011,"color":2012},"s: on hold","A03F0B",{"name":2014,"color":2015},"c: parity","E57949",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.7483865,{"description":2022,"labels":2023,"number":2028,"owner":1988,"repository":1989,"state":1990,"title":2029,"updated_at":2030,"url":2031,"score":2032},"**Expected behaviour:** clicking to reveal new messages that have accumulated would keep my timeline position and let me scroll up to see new messages.\r\n\r\n**Actual behaviour:** clicking on \"Show x new items\" scrolls you up to the present moment of a timeline. You would have to scroll back down to see these messages.\r\n\r\n(Chose the Federated timeline so that new posts would appear more quickly.)\r\n\r\n[screen-capture.webm](https://user-images.githubusercontent.com/5098874/205295772-39bbbb96-1c54-472c-8d5d-69abb82a6d55.webm)\r\n",[2024,2025],{"name":2008,"color":2009},{"name":2026,"color":2027},"p: 1-normal","BFDADC",294,"Timeline position after clicking \"Show x new items\"","2023-01-15T17:57:05Z","https://github.com/elk-zone/elk/issues/294",0.7672801,{"description":2034,"labels":2035,"number":2039,"owner":1988,"repository":1989,"state":1990,"title":2040,"updated_at":2041,"url":2042,"score":2043},"This is for the future, I know that at the moment Elk tries to emulate the behavior of Mastodon, and this is not to be implemented, I discussed this in Discord.\r\n\r\nI've found these tabs confusing, and it's the same thing in Mastodon's web client, they feel unintuitive:\r\n\r\n- **Posts**\r\n- **Posts & Replies**\r\n- **Media**\r\n\r\nIf you click **Posts** and then **Posts & Replies** the view seems to be usually the same. It's as if it didn't do any filtering. Both first two tabs give boosts as well, so if someone boosts all the time, finding their original content is hard. Unless you go the task of hiding boosts, but that's kind of difficult when I'm just previewing what someone has done.\r\n\r\nMy suggestion is to change the tabs to this:\r\n\r\n- **All** (Shows all content)\r\n- **Posts** (shows only users' own posts, not boosts)\r\n- **Replies** (shows only users' replies, not posts or boosts)\r\n- **Boosts** (shows only users boosts)\r\n- **Media** (shows only original media)\r\n\r\nI know these are a lot of choices, but each of those filtering choices would give a unique list of items and would be less confusing.",[2036],{"name":2037,"color":2038},"c: ui","8949BA",975,"Suggestion to change tabs above user's timeline to be able to view users own posts","2023-01-12T19:31:52Z","https://github.com/elk-zone/elk/issues/975",0.7700383,{"description":2045,"labels":2046,"number":2054,"owner":1988,"repository":1989,"state":1990,"title":2055,"updated_at":2056,"url":2057,"score":2058},"On any action made on Elk, today, there is not status shared for screen readers.\r\nOnly things has been done for making UI readable, but nothing (on what I see) had been done for describing status or result of action.\r\n\r\nARIA provides roles for sharing those information: \r\nI found a great resource about and could be great to be implemented:\r\nhttps://a11y-guidelines.orange.com/en/articles/aria-status-messages/\r\n\r\n## [status role](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/status_role)\r\n\r\n- [ ] status publised\r\n- [ ] sharing new tweet available\r\n- [ ] shortcut executed (especially in case of redirection)\r\n #39 : for page navigation sharing also feedback visually like a discreet alert on bottom center\r\n\r\n## [alert role](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/alert_role)\r\n\r\n- [ ] new notification\r\n- [ ] a new reply\r\n\r\nList to be completed",[2047,2048,2051],{"name":2008,"color":2009},{"name":2049,"color":2050},"c: a11y","553F0B",{"name":2052,"color":2053},"s: waiting for user interest","4B02CE",369,"Have ARIA status message to make Elk be fully SR-proof","2023-02-15T14:55:29Z","https://github.com/elk-zone/elk/issues/369",0.77032524,{"description":2060,"labels":2061,"number":2063,"owner":1988,"repository":1989,"state":1990,"title":2064,"updated_at":2065,"url":2066,"score":2067},"It seems Mastodon support reading/writing the timeline read position. ( https://docs.joinmastodon.org/methods/markers/ )\r\n\r\nIt would be great if Elk could use this API endpoint.\r\n\r\nThis way you could scroll through and read your timeline on your computer, then later open the browser on you phone and continue reading the timeline from where you left of.\r\n\r\n\r\n(Apple clients support syncing, but most of them seem to use iCloud for that. But since there is an API endpoint one should be able to make this feature client/OS independent).",[2062],{"name":1985,"color":1986},2219,"Sync timeline read position between sessions/clients","2023-07-10T09:44:18Z","https://github.com/elk-zone/elk/issues/2219",0.7757856,{"description":2069,"labels":2070,"number":2073,"owner":1988,"repository":1989,"state":1990,"title":2074,"updated_at":2075,"url":2076,"score":2077},"Be nice to be able to clear notifications within the Notifications panel or mark them as read.",[2071,2072],{"name":2008,"color":2009},{"name":2014,"color":2015},711,"Ability to clear Notifications, mark as Read","2023-02-04T20:08:39Z","https://github.com/elk-zone/elk/issues/711",0.7801284,{"description":2079,"labels":2080,"number":2083,"owner":1988,"repository":1989,"state":1990,"title":2084,"updated_at":2085,"url":2086,"score":2087},"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.",[2081,2082],{"name":2008,"color":2009},{"name":2037,"color":2038},1355,"Status design and flow","2023-02-03T05:16:28Z","https://github.com/elk-zone/elk/issues/1355",0.7859745,{"description":2089,"labels":2090,"number":2092,"owner":1988,"repository":1989,"state":1990,"title":2093,"updated_at":2094,"url":2095,"score":2096},"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",[2091],{"name":1985,"color":1986},1931,"Filter for Home timeline","2023-04-01T13:48:39Z","https://github.com/elk-zone/elk/issues/1931",0.7863711,["Reactive",2098],{},["Set"],["ShallowReactive",2101],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"tzMm_0-youUI1p8FLPc7jCStJZGkYH8-e8eMSDXMhAM":-1},"/elk-zone/elk/1070"]