To be clear, we still want as many TestFlight crash log submissions as possible, even if they're anonymous. If it's a crash that you can reproduce, submitting a GitHub issue is helpful too :)
TestFlight tries to group similar crash logs together, so crashes that can seem "random" can actually help to form a pattern when put together with all the other logs.
Yes, we can see them! When Mlem crashes on the TestFlight, you will get an option to share crash logs with us. In some cases this is very useful for us because it shows us the entire traceback of the error, which can help us to reproduce the problem.
If you can reproduce an issue consistently we prefer you submit it via GitHub too if possible. GitHub allows us to keep track of which issues we've resolved or not resolved, we're able to ask follow up questions, and you as the reporter are able to see when we've fixed it. If you mention in the GitHub that you've submitted a crash log (and roughly what time you submitted it at, if the crash log was anonymous) then we can find the relevant crash log which is super helpful for us.
We don't really have a notification system set up for TestFlight feedback. I go through it whenever I remember to, but I frequently forget 😅 A lot of people submitted similar crash reports to the one you submitted feedback on, but that particular issue is difficult to reproduce consistently so make take some time to fix.
We're making several quality-of-life tweaks to the iPad layout in 2.0! So far, we've made the image viewer full-screen and updated the sidebar to look a bit more modern. Here's a sneak peek:
There's also a setting for a more compact sidebar layout, if you prefer that:
(This is all WIP, it might change. Ignore the lack of All/Local/Subscribed buttons, those will be back in before the first TestFlight).
We're also adding a setting that displays posts in a grid with two or more columns, which will make the posts look less wide in this format.
Longer-term we're considering some ways that we can improve the iPad layout as a whole - such as having a three-column layout - but there's some navigation problems to work out and we can't promise that anything like that will be in 2.0.
This is related to a change in Lemmy v0.19.4. We've fixed this issue; it'll be live in a day or two.
This isn't possible in Mlem right now, but we can add it to the next beta 👍
Mlem dev here! We're still working on it - a PR is merged every couple of days on our GitHub. It's true that development isn't as active as it used to be in the height of the Reddit migration, which unfortunately leads to new features being announced less frequently, but that's to be expected. We're working towards another release sometime in the coming weeks.
If you noticed any bugs with Mlem and you'd like to report them, you can do so here and we'll look into it 👍
Side note: We don't currently have any plans to drop Lemmy 0.18 support. Supporting 0.18 isn't a major technical challenge for us at the moment, so we don't really have a reason to drop support for it.
This would certainly be a useful feature. Unfortunately, Apple does not make their translation API available for us to use, so we'd have to use someone else's API instead. I haven't looked too deeply into potential options just yet, but have created an issue here to keep track of the suggestion 👍
We have a very small developer team working in our free time, and none of us have any prior knowledge in the area of low-level markdown extensions. It’s very complex, and we’d probably never leave beta if making a perfect markdown renderer was on our requirement list, so we omitted it. It might be possible to work out given enough time, but that’s time that we chose to invest in other areas instead.
If you know of any other non-web apps (iOS or Android) that are able to correctly render all of Lemmy’s markdown, let us know. We may be able to learn from/use their implementation, depending on the license it’s distributed under. I haven’t seen any Lemmy clients that can do this yet.
Spoilers, subscripts and superscripts don’t work, but everything else does.
Markdown in general is unfortunately rather difficult to render. We use an open-source treesitter that parses GitHub-flavored markdown, which is similar to Lemmy’s markdown. Fully supporting the Lemmy markdown specification (spoilers, for example) would probably require us to instead use a custom implementation built directly out of cmark.
Yep, this isn’t possible right now. We’re tracking the issue here, and I’ll try to get it working in the next major update 👍
Thank you for making Lemmy ❤️
Ah, that makes sense! Thanks ❤