",[2882,2885],{"name":2883,"color":2884},"c: ui","8949BA",{"name":2886,"color":2887},"c: parity","E57949",1682,"Filter phrase list","2023-02-18T07:57:05Z","https://github.com/elk-zone/elk/issues/1682",0.74524957,{"description":2894,"labels":2895,"number":2900,"owner":2863,"repository":2864,"state":2865,"title":2901,"updated_at":2902,"url":2903,"score":2904},"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",[2896,2899],{"name":2897,"color":2898},"c: feature","2878FF",{"name":2886,"color":2887},2860,"[Feature request] \"Read more\" button for long post","2025-01-23T15:06:43Z","https://github.com/elk-zone/elk/issues/2860",0.7472235,{"description":2906,"labels":2907,"number":2911,"owner":2863,"repository":2864,"state":2865,"title":2912,"updated_at":2913,"url":2914,"score":2915},"Some alternative descriptions can be really really large:\r\n\r\n\u003Cimg width=\"1754\" alt=\"Capture d’écran, le 2023-01-06 à 11 39 07\" src=\"https://user-images.githubusercontent.com/3556/211056731-fa9403b7-2b4e-4cf9-a923-2f8d62a6c0b8.png\">\r\n\r\nhttps://oisaur.com/@atsemtex/109643074493017591\r\n\r\nMy request is to be able to expand the section when it takes more than one line. For the moment you can see the whole message when putting your cursor hover the truncated text block but it's not super intuitive.",[2908],{"name":2909,"color":2910},"c: a11y","553F0B",829,"Ability to see the whole alt text content for an image","2023-01-27T04:14:20Z","https://github.com/elk-zone/elk/issues/829",0.7484992,{"description":2917,"labels":2918,"number":2920,"owner":2863,"repository":2864,"state":2865,"title":2921,"updated_at":2922,"url":2923,"score":2924},"## Proposal\r\n\r\n1. While composing a post, a red `[ NO ALT ]` badge (see example [here](https://chriscoyier.net/2023/01/25/musing-upon-an-alt-text-badge-on-images/)) should appear on each media without an ALT. When clicked, it will open the Edit dialog (it is basically the same as the Edit button).\r\n\r\n2. When clicking the Publish button, if there are images without ALT text, a dialog will appear that will show each of them with the input text to edit (same dialog as current edit could work) with two buttons: `[ Skip ]` `[ Done ]` (skip should be grayed, dimmed). Maybe for the last image, the Done button should read Publish.\r\n\r\n3. A new preference option should be added for users that would like to avoid the suggestion prompt. This option will be false by default, the feature is opt-out to encourage users. Currently, there is a similar feature in Twitter that is opt-in.\r\n\r\n## Context\r\n\r\nWe run a poll on [Mastodon](https://elk.zone/m.webtoo.ls/@patak/109732787938714669) and [Twitter](https://twitter.com/patak_dev/status/1617136714400600064) about UX to encourage users to add ALT to their attached images.\r\n\r\n\u003Cimg width=\"611\" alt=\"Mastodon poll results, see linked Post above\" src=\"https://user-images.githubusercontent.com/583075/216021585-6840e3ff-37f0-4c47-9b64-399c8d55e10d.png\">\r\n\r\n\u003Cimg width=\"596\" alt=\"Twitter poll results, see linked Tweet above\" src=\"https://user-images.githubusercontent.com/583075/216021418-b73f5c55-7910-437a-afd0-a57e0b7c185e.png\">\r\n\r\nSo suggesting + opt-out seems to be what most users will prefer/accept.\r\n\r\n@antfu [proposed](https://twitter.com/antfu7/status/1617173310235901953): \r\n> having an inline textbox with a placeholder, something like \"Add a description to the media make it more reachable\". Which could be a low intrusion way and no need for a config.\r\n\r\nFollowing a [discussion](https://twitter.com/toddlibby/status/1620721721375588353?s=20) with @colabottles, I think we could do both because the inline suggestion may avoid the prompt appearing in most cases.\r\n",[2919],{"name":2909,"color":2910},1552,"Encourage use of Alt text for attached media","2023-02-02T20:57:34Z","https://github.com/elk-zone/elk/issues/1552",0.75539356,{"description":2926,"labels":2927,"number":2929,"owner":2863,"repository":2864,"state":2865,"title":2930,"updated_at":2931,"url":2932,"score":2933},"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/))",[2928],{"name":2857,"color":2858},1880,"Link length not properly counted in status text","2023-08-01T16:00:30Z","https://github.com/elk-zone/elk/issues/1880",0.7568668,{"description":2935,"labels":2936,"number":2939,"owner":2863,"repository":2864,"state":2865,"title":2940,"updated_at":2941,"url":2942,"score":2943},"I posted a post, in markdown format, using `\\*` to make literal asterisks to indicate multiplication.\r\n\r\nIn the Mastodon client, it looks like this:\r\n\r\n\r\n\r\nHowever, the literal `*` characters in the already marked up output get interpreted as markdown in Elk:\r\n\r\n\r\n\r\nThis leaves me with no way to display consistently what I mean: multiplication.",[2937,2938],{"name":2857,"color":2858},{"name":2860,"color":2861},1509,"Excessive markdown parsing","2023-03-03T10:06:30Z","https://github.com/elk-zone/elk/issues/1509",0.7720095,{"description":2945,"labels":2946,"number":2952,"owner":2863,"repository":2864,"state":2865,"title":2953,"updated_at":2954,"url":2955,"score":2956},"### Clear and concise description of the problem\n\nMastodon allows you to choose what part of an image will always show when cropped. I like using this feature! Elk doesn't seem to support this.\n\n### Suggested solution\n\nAdd the little circle Mastodon has on images when editing the description, so we can choose what parts of our images are focused on when they're cropped.\n\n### Alternative\n\n_No response_\n\n### Additional context\n\nHere is what the focus editor (?) looks like on Mastodon:\r\n\r\n\u003Cimg width=\"985\" alt=\"image\" src=\"https://user-images.githubusercontent.com/122533181/212341960-62baaea8-b04c-4a58-8229-117df085b1dd.png\">\r\n",[2947,2948,2951],{"name":2897,"color":2898},{"name":2949,"color":2950},"p: 1-normal","BFDADC",{"name":2860,"color":2861},1080,"Add a way to choose where an image is focused","2023-01-13T15:09:21Z","https://github.com/elk-zone/elk/issues/1080",0.7720301,{"description":2958,"labels":2959,"number":2961,"owner":2863,"repository":2864,"state":2865,"title":2962,"updated_at":2963,"url":2964,"score":2965},"When PreviewCard is detected to be a mastodon link (via powers of regex testing the author or provider or title?) we can expand the preview card in a manner similar to Twitter\n\nFrom previous discussion:\n1. don't implement a quote button\n2. aim to have expanded mastodon links",[2960],{"name":2897,"color":2898},387,"Expand mastodon links","2023-08-19T07:45:13Z","https://github.com/elk-zone/elk/issues/387",0.7736729,["Reactive",2967],{},["Set"],["ShallowReactive",2970],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fPlnQRjqrHa8YBnvrJUFexdNWfUKG78f9DxeFMQg2bZQ":-1},"/elk-zone/elk/1385"]