",[1984,1987],{"name":1985,"color":1986},"c: ui","8949BA",{"name":1988,"color":1989},"c: parity","E57949",1682,"elk-zone","elk","open","Filter phrase list","2023-02-18T07:57:05Z","https://github.com/elk-zone/elk/issues/1682",0.74490327,{"description":1999,"labels":2000,"number":2007,"owner":1991,"repository":1992,"state":1993,"title":2008,"updated_at":2009,"url":2010,"score":2011},"Found a report Mastodon web does not apply filters on the Explore posts tab, and Elk is the same\n\nSee post here: https://elk.zone/mastodon.world/@Colby/109961079216371237\n\nHowever I think the Explore tab counts as a public timeline and should be filtered.",[2001,2004],{"name":2002,"color":2003},"c: bug","FFA500",{"name":2005,"color":2006},"p: 1-normal","BFDADC",1851,"apply filters to the #Explore posts","2023-03-04T14:47:21Z","https://github.com/elk-zone/elk/issues/1851",0.7579732,{"description":2013,"labels":2014,"number":2016,"owner":1991,"repository":1992,"state":1993,"title":2017,"updated_at":2018,"url":2019,"score":2020},"Not to be overly pedantic but the URL matching overshoots a bit when compared to mastodon. Specifically, in this example, mastodon would not capture the right paren `)`:\r\n```\r\nfoo (https://news.ycombinator.com/)\r\n```\r\n\r\nMastodon counts 29 characters (500 - 471):\r\n\r\n\r\nElk counts 28:\r\n\r\n\r\nThis is an issue since now it's possible to achieve a elk-safe 500 character limit and then receive a 500 character limit exceeded error by Mastodon after submitting which would confuse the user.\r\n\r\nSo somewhere down the line we might need to update this:\r\nhttps://github.com/elk-zone/elk/blob/3732a2cc16b4de6cd60f4836151d4a3292c627fa/components/publish/PublishWidget.vue#L72\r\n\r\nSince it includes the ending paren:\r\n\r\n\r\nMastodon themselves have their URL regex defined here: https://github.com/mastodon/mastodon/blob/1ed12d/app/javascript/mastodon/features/compose/util/url_regex.js (which relies on [`twitter-text`](https://github.com/twitter/twitter-text/))",[2015],{"name":2002,"color":2003},1880,"Link length not properly counted in status text","2023-08-01T16:00:30Z","https://github.com/elk-zone/elk/issues/1880",0.76190513,{"description":2022,"labels":2023,"number":2028,"owner":1991,"repository":1992,"state":1993,"title":2029,"updated_at":2030,"url":2031,"score":2032},"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.",[2024,2027],{"name":2025,"color":2026},"c: feature","2878FF",{"name":1985,"color":1986},1355,"Status design and flow","2023-02-03T05:16:28Z","https://github.com/elk-zone/elk/issues/1355",0.77332765,{"description":2034,"labels":2035,"number":2040,"owner":1991,"repository":1992,"state":1993,"title":2041,"updated_at":2042,"url":2043,"score":2044},"Using elk I replied to a post that had been boosted by a friend, removed the original poster from my reply and mentioned the friend.\r\n\r\nIn elk, this mention isn't visible, whereas in the mastodon UI it is. It looks like a reply to the original post with no indication that I mentioned the friend.\r\n\r\nConcrete example:\r\nhttps://hachyderm.io/@ross/110310075165327904\r\nhttps://elk.zone/hachyderm.io/@ross/110310075165327904\r\n",[2036,2037],{"name":2002,"color":2003},{"name":2038,"color":2039},"s: pending triage","dddddd",2059,"Doesn't show mentions in reply","2023-05-04T11:05:34Z","https://github.com/elk-zone/elk/issues/2059",0.7786791,{"description":2046,"labels":2047,"number":2055,"owner":1991,"repository":1992,"state":1993,"title":2056,"updated_at":2057,"url":2058,"score":2059},"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",[2048,2049,2052],{"name":2025,"color":2026},{"name":2050,"color":2051},"c: a11y","553F0B",{"name":2053,"color":2054},"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.7823853,{"description":2061,"labels":2062,"number":2064,"owner":1991,"repository":1992,"state":1993,"title":2065,"updated_at":2066,"url":2067,"score":2068},"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",[2063],{"name":2038,"color":2039},1931,"Filter for Home timeline","2023-04-01T13:48:39Z","https://github.com/elk-zone/elk/issues/1931",0.7836598,{"description":2070,"labels":2071,"number":2073,"owner":1991,"repository":1992,"state":2074,"title":2075,"updated_at":2076,"url":2077,"score":2078},"It appears we are displaying a status containing sensitive media as if it is a spoiler, even though it has no CW / `spoiler_text`\r\n\r\nImplement logic so that Only the sensitive media is hidden/blurred instead of the whole status.\r\n\r\n## On Elk:\r\n\r\nhttps://elk.zone/fosstodon.org/@ayodev@mas.to/109457552157025274\r\n\r\n\r\n\r\n\r\n## On Mastodon:\r\n\r\nhttps://mas.to/@ayodev/109457552070990933\r\n\r\n\r\n\r\n",[2072],{"name":2002,"color":2003},318,"closed","Only blur/hide sensitive media instead of the whole status","2022-12-29T16:31:05Z","https://github.com/elk-zone/elk/issues/318",0.6734447,{"description":2080,"labels":2081,"number":2083,"owner":1991,"repository":1992,"state":2074,"title":2084,"updated_at":2085,"url":2086,"score":2087},"\r\n\r\nIn [this post](https://elk.zone/social.ayco.io/@ayo/109677886156981992) I added a content warning text with the word \"Twitter\". Compare with [mastodon web](https://social.ayco.io/@ayo/109677886156981992)\r\n\r\nHowever I also have a filter for the word \"Twitter\" so the Status object will have a `filtered` property. \r\n\r\nCouple of things need to be fixed here, but I think could be done together \r\n- [ ] the author (me) should _not_ be filtered by his filters\r\n- [ ] the content warning should be prioritized over the filter phrase\r\n\r\nI think the second one is a regression 🤔",[2082],{"name":2002,"color":2003},1027,"Filter and Content Warning logic is wrong","2023-02-05T15:05:44Z","https://github.com/elk-zone/elk/issues/1027",0.6840205,{"description":2089,"labels":2090,"number":2093,"owner":1991,"repository":1992,"state":2074,"title":2094,"updated_at":2095,"url":2096,"score":2097},"I have a filter setting for Mastodon to not show Toots with the word \"Twitter\".\n\nI have tested on three clients and implementation is not always there. See screenshots below\n\n\n\nThis is successfully implemented in one mobile app client I am using (Toot!). See \"Removed by filter\"\n\n\n\nBut not on Elk it is not\n\n\n\nI also found another mobile client (Tooot) that fails to implement filter \n\n",[2091,2092],{"name":2025,"color":2026},{"name":2005,"color":2006},163,"feat: Content Filters","2022-12-04T19:28:27Z","https://github.com/elk-zone/elk/issues/163",0.7510112,["Reactive",2099],{},["Set"],["ShallowReactive",2102],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"p0MxpU0IuTqshNF8HIhD8eMT4hBf8jtTKHusbMDzdxY":-1},"/elk-zone/elk/334"]