",[2004,2007],{"name":2005,"color":2006},"c: ui","8949BA",{"name":1991,"color":1992},1682,"Filter phrase list","2023-02-18T07:57:05Z","https://github.com/elk-zone/elk/issues/1682",0.7384993,{"description":2014,"labels":2015,"number":2018,"owner":1994,"repository":1995,"state":1996,"title":2019,"updated_at":2020,"url":2021,"score":2022},"Some mastodon instances allow a long post, whose character limit can be over 5000. Request to add a \"read more\" / \"show more\" button in this case.\r\n\r\n[test post](https://mastodon.ktachibana.party/@furretya/112283693211261234)\r\n\r\nexamples:\r\n\u003Cimg width=\"601\" alt=\"Screenshot 2024-05-02 at 5 44 51 PM\" src=\"https://github.com/elk-zone/elk/assets/10359255/74a2c074-00cb-45a6-bb51-de63e644757f\">\r\n\r\n\u003Cimg width=\"814\" alt=\"Screenshot 2024-05-02 at 5 46 50 PM\" src=\"https://github.com/elk-zone/elk/assets/10359255/f451bd5d-cc1a-42ca-bbaf-3fc472a86881\">\r\n\r\nCode references:\r\n\r\nmastodon:\r\n\r\nhttps://github.com/mastodon/mastodon/blob/4b2054ee57b41c304f85eab6236baebe0b732d95/app/javascript/mastodon/components/status_content.jsx#L135-L139\r\n\r\nmisskey:\r\n\r\nhttps://github.com/misskey-dev/misskey/blob/c530a46e547791b22ecf12fe1b9e952f7df0a58c/packages/frontend/src/components/MkContainer.vue#L89-L94\r\n",[2016,2017],{"name":1985,"color":1986},{"name":1991,"color":1992},2860,"[Feature request] \"Read more\" button for long post","2025-01-23T15:06:43Z","https://github.com/elk-zone/elk/issues/2860",0.73943585,{"description":2024,"labels":2025,"number":2027,"owner":1994,"repository":1995,"state":1996,"title":2028,"updated_at":2029,"url":2030,"score":2031},"The only hashtag-feed I’m interested in following on mastodon right now is #rustlang+#gamedev\r\n\r\nI.e. any post containing *both* those tags. This type of narrow search is very useful for low-touch users of Mastodon like myself, so I can follow a feed that can quickly be 100% read with a daily/weekly check-in.\r\n\r\nPrior art in official Mastodon-web, ‘Enable advanced web interface’ toggled on:\r\n\r\n\r\nhttps://github.com/rust-gamedev/wg/issues/131#issuecomment-1345338530\r\n\r\nAside from setting this up as a personal feed, it'd also be very useful as a publicly accessible feed that anyone can follow without signin, e.g. `https://mastodon.social/tags/gamedev+rustlang`\r\n\r\nSee also: https://github.com/mastodon/mastodon/issues/6287",[2026],{"name":1985,"color":1986},905,"Tag-combination feeds","2023-02-04T21:06:46Z","https://github.com/elk-zone/elk/issues/905",0.7421331,{"description":2033,"labels":2034,"number":2038,"owner":1994,"repository":1995,"state":1996,"title":2039,"updated_at":2040,"url":2041,"score":2042},"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/))",[2035],{"name":2036,"color":2037},"c: bug","FFA500",1880,"Link length not properly counted in status text","2023-08-01T16:00:30Z","https://github.com/elk-zone/elk/issues/1880",0.7434212,{"description":2044,"labels":2045,"number":2048,"owner":1994,"repository":1995,"state":1996,"title":2049,"updated_at":2050,"url":2051,"score":2052},"> Question for Mastodon experts, is there a way to get some sort of notification feed for mutuals only? I love my general notifs but it’s hard to keep up and I often miss replies from good friends. I’d love a way to skim just those in addition to the general notifs\r\n> \r\n> I mean notifications for replies only btw, not for friends’ main Mastodon posts 😅. Friends reply to me and their replies get lost in the notification feed. So looking for a solution where I can sort replies into “general” and “mutuals only” if that makes sense\r\n\r\nhttps://elk.zone/mastodon.roe.dev/@taylorlorenz@mastodon.social/109546296369812851",[2046,2047],{"name":1985,"color":1986},{"name":1988,"color":1989},473,"'mutuals' notification tab","2023-02-04T20:51:01Z","https://github.com/elk-zone/elk/issues/473",0.74854183,{"description":2054,"labels":2055,"number":2061,"owner":1994,"repository":1995,"state":1996,"title":2062,"updated_at":2063,"url":2064,"score":2065},"The (my?) default mastodon instance offers a link to automatically extract text from an image to use as alt text.\r\nIt seems to download some tesseract wasm code to do the parsing. Very helpful if the image mainly contains text",[2056,2057,2060],{"name":1985,"color":1986},{"name":2058,"color":2059},"s: pending triage","dddddd",{"name":1991,"color":1992},1385,"Feature request: add a 'extract text from image' link/button ","2023-02-04T22:56:49Z","https://github.com/elk-zone/elk/issues/1385",0.75027317,{"description":2067,"labels":2068,"number":2071,"owner":1994,"repository":1995,"state":1996,"title":2072,"updated_at":2073,"url":2074,"score":2075},"When you are in a DM, if you tag a user, that user also receives the DM and is later on part of the thread. It is consistent with the way Mastodon works, but a lot of users are going to be surprised (in Discord, Slack, Twitter, etc... tagging someone in a DM doesn't have this effect). This happened to me a few times already, last time with @spences10 and @oliverturner.\r\n\r\nI think we should ask for confirmation if a user tags someone new in a DM\r\n",[2069,2070],{"name":1985,"color":1986},{"name":1988,"color":1989},288,"Confirmation before adding a user to a DM thread","2022-12-02T08:21:49Z","https://github.com/elk-zone/elk/issues/288",0.7548832,{"description":2077,"labels":2078,"number":2080,"owner":1994,"repository":1995,"state":1996,"title":2081,"updated_at":2082,"url":2083,"score":2084},"### Clear and concise description of the problem\n\nOn Twitter, there's a nice feature: after you write a tweet, you can click a button to add another tweet under that one, so you can write a fairly long thread (I think 25ish tweets?) before sending it. I used this feature a lot and liked it very much.\r\n\r\nOn regular Mastodon, you have to send your first toot before you can start drafting the next one. Because I like to finish writing threads before I post them, I often use a workaround of composing my threads in my computer's notes app, then pasting individual toots in one at a time. This is kind of annoying to have to do. :(\r\n\r\nI think it would be very cool if Elk supported draft threads like on Twitter!\n\n### Suggested solution\n\nAdd a little \"add toot\" button when composing a toot, then allow some number of subsequent toots to be drafted before posting.\n\n### Alternative\n\n_No response_\n\n### Additional context\n\n_No response_",[2079],{"name":2058,"color":2059},1073,"Compose thread before sending","2023-03-13T21:54:55Z","https://github.com/elk-zone/elk/issues/1073",0.7557735,{"description":2086,"labels":2087,"number":2090,"owner":1994,"repository":1995,"state":1996,"title":2091,"updated_at":2092,"url":2093,"score":2094},"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.",[2088,2089],{"name":1985,"color":1986},{"name":2005,"color":2006},1355,"Status design and flow","2023-02-03T05:16:28Z","https://github.com/elk-zone/elk/issues/1355",0.7569261,["Reactive",2096],{},["Set"],["ShallowReactive",2099],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"VlDhCDhtzF6lb4FpTQz-Lrmv-WvyRNhYIj1F0l3-_Zo":-1},"/elk-zone/elk/47"]