",[2009,2010],{"name":1996,"color":1997},{"name":1999,"color":2000},1680,"Tag important for context is removed","2023-02-08T21:56:12Z","https://github.com/elk-zone/elk/issues/1680",0.78405434,{"description":2017,"labels":2018,"number":2021,"owner":1985,"repository":1986,"state":1987,"title":2022,"updated_at":2023,"url":2024,"score":2025},"### Pre-Checks\n\n- [X] Check that there isn't [already an issue](https://github.com/elk-zone/elk/issues) that reports the same bug to avoid creating a duplicate.\n- [X] Check that this is a concrete bug. For Q&A open a [GitHub Discussion](https://github.com/elk-zone/elk/discussions) or join our [Discord Chat Server](https://chat.elk.zone).\n- [X] Providing a screenshot or video to reproduce the issue or show visually what was meant.\n- [ ] I am willing to provide a PR.\n\n### Describe the bug\n\nI (too often) end up trying to scroll up on a thread (or want to \"pull to refresh\" on the thread) and end up triggering the default Chrome (I'm on Android 13) pull-to-refresh on the thread. This breaks any backward navigation and context (timeline position, etc).\r\n\r\nIt would be great if there was an \"app\" implemented pull-to-refresh that wouldn't break the above or something. Related, because there are no spinners or other progress indicators when opening a thread, I end up triggering the above more often, because I think I should be able to scroll to get to the root thread, but it hasn't loaded yet.\n\n### Reproduction video or screenshot\n\n_No response_\n\n### Additional Context\n\n_No response_",[2019,2020],{"name":1996,"color":1997},{"name":1999,"color":2000},1187,"PWA: Refreshing when on a thread breaks back nav and loses timeline position","2023-01-17T00:48:39Z","https://github.com/elk-zone/elk/issues/1187",0.7881569,{"description":2027,"labels":2028,"number":2030,"owner":1985,"repository":1986,"state":1987,"title":2031,"updated_at":2032,"url":2033,"score":2034},"Replies in threads are replies to all. Ordinarily, not a problem, but suppose I want to affirm someone else's specific experience with my own by replying just to them, and replying to the OP with my individual experience in general: everyone gets everything. Replying to OP is to OP; replying to anyone who replied to OP goes to everyone. \r\n\r\nThis is like 'reply all', and I can attest to the fact that I was there when someone at Microsoft HR sent out an e-mail to 30,000 people and some folks replied all to take them off the e-mail distribution list, others chimed in 'me, too' and on and on until the e-mail system crashed. Be real nice if I could prune the 'reply to' and target my response.\r\n\r\nI think this would make replying to a post more specific and precise. No rush, though. \r\n\r\n\r\n\r\n",[2029],{"name":1999,"color":2000},2309,"Allow posters to edit to whom they are replying","2023-08-07T07:58:28Z","https://github.com/elk-zone/elk/issues/2309",0.7925575,{"description":2036,"labels":2037,"number":2042,"owner":1985,"repository":1986,"state":2043,"title":2044,"updated_at":2045,"url":2046,"score":2047},"See: https://elk.zone/m.webtoo.ls/@bencodezen/109626135795293817\r\nIt will only show that post (a reply)\r\nIf you get to it from Notifications or Home, it shows the full thread. Reload and you'll only see the single post.",[2038,2039],{"name":1996,"color":1997},{"name":2040,"color":2041},"p: 2-high","FF4d4d",742,"closed","Direct navigation to post doesn't expand context","2023-01-04T19:55:59Z","https://github.com/elk-zone/elk/issues/742",0.7487916,{"description":2049,"labels":2050,"number":2052,"owner":1985,"repository":1986,"state":2043,"title":2053,"updated_at":2054,"url":2055,"score":2056},"If you boost a post, and your own reply to that post, then your reply should appear inside the original post rather than as a separate boost.\r\n\r\nIt'd look great! That's the only reason really.\r\n\r\n(Kinda like a \"threaded view\", but only for one reply.)",[2051],{"name":1999,"color":2000},2030,"Merge boosted replies into boost","2023-04-29T21:38:36Z","https://github.com/elk-zone/elk/issues/2030",0.7589575,{"description":2058,"labels":2059,"number":2063,"owner":1985,"repository":1986,"state":2043,"title":2064,"updated_at":2065,"url":2066,"score":2067},"Currently, nearby replies are connected together on the home page, which is great!\r\nIt seems like this doesn't happen on user's profile pages.\r\n\r\nI think we should enable it there as well.\r\n\r\n(For reference: twitter does)",[2060],{"name":2061,"color":2062},"c: ui","8949BA",637,"Nearby replies on profile pages should be connected","2022-12-29T16:26:39Z","https://github.com/elk-zone/elk/issues/637",0.7611926,{"description":2069,"labels":2070,"number":2077,"owner":1985,"repository":1986,"state":2043,"title":2078,"updated_at":2079,"url":2080,"score":2081},"UI in Twitter with a line showing the connection between messages\r\n\r\n\r\nAn example from another [mastodon client](https://mas.to/@ayo@fosstodon.org/109341743160486404)\r\n",[2071,2074],{"name":2072,"color":2073},"c: feature","2878FF",{"name":2075,"color":2076},"p: 1-normal","BFDADC",47,"UI elements to help understand threads","2023-01-30T12:56:53Z","https://github.com/elk-zone/elk/issues/47",0.7687662,{"description":2083,"labels":2084,"number":2086,"owner":1985,"repository":1986,"state":2043,"title":2087,"updated_at":2088,"url":2089,"score":2090},"`{0} posts` is different from other ones\r\n\r\n\r\n",[2085],{"name":2061,"color":2062},763,"Account page stats should probably have the same casing","2023-02-04T21:09:53Z","https://github.com/elk-zone/elk/issues/763",0.7739881,["Reactive",2092],{},["Set"],["ShallowReactive",2095],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"biKf4LHzi9IK-Mb_y57G6v7Mc3CczYYXLiuE5VDscD0":-1},"/elk-zone/elk/593"]