",[1998,1999],{"name":1985,"color":1986},{"name":2000,"color":2001},"s: pending triage","dddddd",1680,"Tag important for context is removed","2023-02-08T21:56:12Z","https://github.com/elk-zone/elk/issues/1680",0.7645104,{"description":2008,"labels":2009,"number":2012,"owner":1988,"repository":1989,"state":1990,"title":2013,"updated_at":2014,"url":2015,"score":2016},"It seems that the translation feature incorrectly tries to translate linked user handles, it seems like usernames that are linked should just be skipped when translating since any modification would make the user's handle incorrect\r\n\r\nExample:\r\n\r\n",[2010,2011],{"name":1985,"color":1986},{"name":2000,"color":2001},2185,"Translate changes tagged usernames","2023-07-08T04:32:13Z","https://github.com/elk-zone/elk/issues/2185",0.7871555,{"description":2018,"labels":2019,"number":2026,"owner":1988,"repository":1989,"state":1990,"title":2027,"updated_at":2028,"url":2029,"score":2030},"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.",[2020,2023],{"name":2021,"color":2022},"c: feature","2878FF",{"name":2024,"color":2025},"c: ui","8949BA",1355,"Status design and flow","2023-02-03T05:16:28Z","https://github.com/elk-zone/elk/issues/1355",0.78962296,{"description":2032,"labels":2033,"number":2035,"owner":1988,"repository":1989,"state":1990,"title":2036,"updated_at":2037,"url":2038,"score":2039},"When the compose message window is opened, I can't see anymore which message I'm answering to:\r\n\r\n\u003Cimg width=\"1455\" alt=\"Capture d’écran, le 2023-01-06 à 14 00 57\" src=\"https://user-images.githubusercontent.com/3556/211081276-3a7bf6bb-6b6f-4220-a581-2a0c26cab925.png\">\r\n\r\nThis is a bit harder to memorize the initial message for an accurate answer, especially long form ones.\r\n\r\nI propose to put the message you're answering to just above the compose form (or at least to keep it visible behind it…).",[2034],{"name":2024,"color":2025},833,"When answering a message, make the initial message visible","2023-01-07T22:08:22Z","https://github.com/elk-zone/elk/issues/833",0.7924262,{"description":2041,"labels":2042,"number":2044,"owner":1988,"repository":1989,"state":2045,"title":2046,"updated_at":2047,"url":2048,"score":2049},"A friend posted a cheeky msg that contained a fictional html tag as a way to say hello to their community, see the screenshots below:\r\n\r\n### Elk UI:\r\n\r\n\u003Cimg width=\"648\" alt=\"Screen Shot 2022-12-05 at 10 56 32 AM\" src=\"https://user-images.githubusercontent.com/220900/205683516-513589da-e4d9-4dec-b2b1-39bdb40a2a9b.png\">\r\n\r\n### Mastodon UI:\r\n\r\n\u003Cimg width=\"537\" alt=\"Screen Shot 2022-12-05 at 10 56 55 AM\" src=\"https://user-images.githubusercontent.com/220900/205683562-dc4ca3c6-a78a-4e33-9e8f-2e0f1a32339c.png\">\r\n\r\n\u003Cbr />\r\n\u003Cbr />\r\n\r\nI believe the Mastodon UI captured the correct intention here, which was to have a message displaying the tag as plain text. I totally get how it might be tricky to both support html tags and not strip invalid tags, I mostly just wanted to bring this up to other people's attention. If anyone has a strong argument to not support this, feel free to close it 😊 \r\n\r\nPossibly related to https://github.com/elk-zone/elk/issues/256\r\n",[2043],{"name":1985,"color":1986},346,"closed","Should not remove arbitrary html-tag-like text","2022-12-20T00:23:13Z","https://github.com/elk-zone/elk/issues/346",0.7401328,{"description":2051,"labels":2052,"number":2054,"owner":1988,"repository":1989,"state":2045,"title":2055,"updated_at":2056,"url":2057,"score":2058},"## Steps to reproduce\r\n\r\n1. write a post including a reference to somebody not on your instance\r\n\r\n\u003Cimg width=\"679\" alt=\"Capture d’écran, le 2023-01-08 à 12 45 36\" src=\"https://user-images.githubusercontent.com/3556/211211027-f8bd7389-a635-4f24-b2fd-ce4e0409abf3.png\">\r\n\r\n2. click Delete and rewrite\r\n\r\n\u003Cimg width=\"310\" alt=\"Capture d’écran, le 2023-01-08 à 12 45 43\" src=\"https://user-images.githubusercontent.com/3556/211211037-9ab1205a-e13a-4eec-adaa-adc0acde0935.png\">\r\n\r\n3. the message only contains the handle `@foo` and not the complete address `@foo@example.com` which leads to an undetected handle/link once submitted\r\n\r\n\u003Cimg width=\"831\" alt=\"Capture d’écran, le 2023-01-08 à 12 45 51\" src=\"https://user-images.githubusercontent.com/3556/211211044-81f253da-54e7-4a9f-bd3b-c851bd6583a3.png\">\r\n\r\n## What I was hoping for\r\n\r\nEither the message in the textarea contains the full address or even better it displays the handle only but detects the full address from the original post.",[2053],{"name":1985,"color":1986},883,"When Deleting and rewriting message usernames are not anymore linked","2023-01-08T19:53:55Z","https://github.com/elk-zone/elk/issues/883",0.7654734,{"description":2060,"labels":2061,"number":2062,"owner":1988,"repository":1989,"state":2045,"title":2063,"updated_at":2064,"url":2065,"score":2066},"We need to properly implement DMs, with better styling, but at least the visibility of the message should default to the message you are replying to.",[],192,"Replying to a direct messages defaults to public","2022-11-28T09:57:44Z","https://github.com/elk-zone/elk/issues/192",0.77769184,{"description":2068,"labels":2069,"number":2077,"owner":1988,"repository":1989,"state":2045,"title":2078,"updated_at":2079,"url":2080,"score":2081},"Before an account's first interaction with an instance, its older toots aren't synced to the instance, and leads to toot timelines like this one:\r\n\r\n\u003Cimg width=\"600\" alt=\"image\" src=\"https://user-images.githubusercontent.com/70191398/210549566-b39028da-3170-4b7e-9308-6652b538a1e0.png\">\r\n\r\nIt would be helpful if the message could be amended to make users aware of the fact and link them to the original site in order to view older toots, like the message on Mastodon.\r\n\r\n\u003Cimg width=\"344\" alt=\"Screenshot 2023-01-04 at 19 55 45\" src=\"https://user-images.githubusercontent.com/70191398/210549912-8c180f0b-dea6-4aa8-9384-ec60b91ca135.png\">",[2070,2073,2074],{"name":2071,"color":2072},"good first issue","7057ff",{"name":2024,"color":2025},{"name":2075,"color":2076},"p: 1-normal","BFDADC",766,"Older unfederated toots aren't linked to","2023-01-04T13:21:04Z","https://github.com/elk-zone/elk/issues/766",0.7802382,{"description":2083,"labels":2084,"number":2086,"owner":1988,"repository":1989,"state":2045,"title":2087,"updated_at":2088,"url":2089,"score":2090},"When posting this link https://www.opendemocracy.net/en/oureconomy/corporate-monopolies-are-threat-to-democracy-public-interest/ here https://fosstodon.org/@Brendanjones/110135158010222739, it was displayed in the link preview on Elk like this, missing the header and subheader:\r\n\r\n\u003Cimg width=\"595\" alt=\"Screenshot 2023-04-03 at 15 40 14\" src=\"https://user-images.githubusercontent.com/16049594/229528521-8aa73a38-096e-425c-a042-28eba3ad9dff.png\">\r\n\r\nI thought it might be a problem with that website but on Mastodon native it looks fine:\r\n\r\n\u003Cimg width=\"578\" alt=\"Screenshot 2023-04-03 at 15 41 51\" src=\"https://user-images.githubusercontent.com/16049594/229528533-d9d9d203-258a-4405-9b38-4080535c92aa.png\">\r\n\r\nAlso displays fine on the birdsite (nope, didn't post, I'm not using that website anymore, just for Elk bug testing :p ):\r\n\r\n\u003Cimg width=\"528\" alt=\"Screenshot 2023-04-03 at 15 43 03\" src=\"https://user-images.githubusercontent.com/16049594/229528569-923379e9-5048-499c-93bd-09470b2e0b3e.png\">",[2085],{"name":1985,"color":1986},1948,"Link preview not displaying correctly","2023-04-29T20:58:09Z","https://github.com/elk-zone/elk/issues/1948",0.7865449,["Reactive",2092],{},["Set"],["ShallowReactive",2095],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"nC57uBnrVFjAVSeNpR6muuBIkvwpJKpu9bjKg7ZCnRs":-1},"/elk-zone/elk/899"]