",[2044,2045],{"name":1985,"color":1986},{"name":2003,"color":2004},1680,"Tag important for context is removed","2023-02-08T21:56:12Z","https://github.com/elk-zone/elk/issues/1680",0.7762945,{"description":2052,"labels":2053,"number":2058,"owner":1988,"repository":1989,"state":1990,"title":2059,"updated_at":2060,"url":2061,"score":2062},"This is a side effect of some other navigation/UX issues I ran into, but when getting routed to the wrong feed (or the app minimizing itself randomly) when I reopen the app it refreshes my feed, and I lose the item I was reading.\r\n\r\nIs it possible to temporarily store a session variable that holds the id of the post that is centered on the screen? \r\n\r\nI'm trying to think of the best way to track this, but I know it's something that Fedilab recently added to their app. As you scroll through your feed, it tracks your current position fairly well (not sure where the trigger point is), and if you go into a thread or suspend the app, it resumes where you were instead of refreshing the feed you're looking at. The refresh behavior is frustrating if you're reading something that is really interesting and for one reason or another get bumped to the wrong place and then lose your place in your feed.",[2054,2055],{"name":2025,"color":2026},{"name":2056,"color":2057},"p: 2-high","FF4d4d",653,"Remember user's last viewed location in feed","2023-05-26T16:20:02Z","https://github.com/elk-zone/elk/issues/653",0.7776803,{"description":2064,"labels":2065,"number":2067,"owner":1988,"repository":1989,"state":1990,"title":2068,"updated_at":2069,"url":2070,"score":2071},"I would recommend following @pluralistic@mamot.fr to see this in action. Cory does these Twitter-style megathreads where the current implementation breaks somewhat...\r\n\r\n- if there are no replies *other than* the thread itself, reorderedTimeline will sort them from 1/x to x/x correctly, but this will completely hog the timeline\r\n- if the thread has a title/content warning, every toot will still need to be clicked for Show more, one by one\r\n- and if any replies get inserted into the timeline, for example because of a boost (as in the screenshot), it will break the sort, as the reply and its boost will be more fresh than any of the original megathread toots\r\n\r\n\r\n\r\nI would suggest that majority of the toots should simply be hidden from view on the timeline and directed toward the \"Show full thread\" page. And on that page, I'd further suggest that \"Show more\" should auto-expand for the whole thread, because the view demonstrated [here](https://elk.zone/mas.to/@pluralistic@mamot.fr/109665054505293039) isn't very useful...\r\n\r\n\r\n",[2066],{"name":2000,"color":2001},966,"reorderedTimeline with megathreads","2023-01-11T10:43:12Z","https://github.com/elk-zone/elk/issues/966",0.77884847,{"description":2073,"labels":2074,"number":2076,"owner":1988,"repository":1989,"state":2077,"title":2078,"updated_at":2079,"url":2080,"score":2081},"Deleting and redrafting a reply to a post does not reply to the post but instead creates a new separate post that only mentions the account handle being replied to.\r\n\r\nTo reproduce:\r\n1. Reply to a post.\r\n2. Click \"Delete and Redraft\".\r\n3. Edit the post and Publish.\r\n\r\nNotice the post does not reply to the original post as it should. It is not shown in the replies. Instead, it is a separate post.",[2075],{"name":1985,"color":1986},2023,"closed","Delete and Re-draft replies does not reply to post","2023-04-28T03:25:55Z","https://github.com/elk-zone/elk/issues/2023",0.6735242,{"description":2083,"labels":2084,"number":2087,"owner":1988,"repository":1989,"state":2077,"title":2088,"updated_at":2089,"url":2090,"score":2091},"### 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- [X] I am willing to provide a PR.\n\n### Describe the bug\n\nSTR:\r\n\r\n1. Reply to a toot.\r\n2. Select \"delete and re-draft\" on the reply.\r\n3. Change something, or don't.\r\n4. Publish the re-drafted reply\r\n\r\nExpected result:\r\n5. Re-drafted toot is tooted as a reply to the original toot.\r\n\r\nActual result:\r\n5. Re-drafted toot is tooted as a standalone toot.\r\n6. @-reply at the beginning of the re-drafted toot is broken -- the first @ is dropped.\n\n### Reproduction video or screenshot\n\nI can make a video if necessary but I think the description above is clear -- let me know if not?\n\n### Additional Context\n\nIf I can figure out how, I'd be glad to contribute to fixing this.",[2085,2086],{"name":1985,"color":1986},{"name":2003,"color":2004},1280,"Deleting and re-drafting a reply breaks thread","2023-07-31T21:45:06Z","https://github.com/elk-zone/elk/issues/1280",0.7154936,["Reactive",2093],{},["Set"],["ShallowReactive",2096],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"JmN8l1U-kQ0tgCwm2NM25XjraPSe8vjrDukihWVJoNg":-1},"/elk-zone/elk/399"]