Skip Navigation

User banner
Posts
86
Comments
284
Joined
2 yr. ago

  • This behavior can be customized under Settings -> Links -> Tappable Links. By default it uses "contextual," which will display the full link in large contexts and just the title in compact contexts (e.g., comments if you have comment display set to "compact"). Setting it to "large" will always display the full link regardless of context.

  • It is our policy not to make features-for-donations transactions, as we feel that would compromise the spirit of the project and set a dangerous precedent that could lead to development becoming beholden to the wealthiest donors. We really appreciate your enthusiasm and your generosity, though--we're going to be busy for a little while getting 2.0 up and running, but we can tentatively scope widgets for 2.1!

  • It's currently live on the TestFlight beta! We're planning to roll it out to the App Store in the next few days.

    1. Yes! We aren't happy with the current state of our media viewer. 2.0 is a backend-focused rewrite, so probably won't have a new media viewer on launch, but it's without a doubt high on our list of important features.
    2. Hard to say. Our iOS compatibility policy guarantees compatibility until iOS18 reaches 75% market share; after that, I can't make any promises. We take the decision to drop compatibility very seriously, and try to only do so when the features offered by the newer iOS are valuable enough that we would be compromising the potential quality of the app by ignoring them.
    3. Yes. We're still working out some UX concerns stemming from the fact that it's very slow to search posts and comments compared to communities, but it's in the plans.
  • We maintain a client-side list of instances supported by lemmy-status.org. Looks like we just forgot to add toast.ooo--should be fixed in the next build.

  • Update to Sjmarf's earlier comment: I have finally tracked down the source of the slowdown, and the fix should be out in the next TestFlight build.

  • It was not, nice catch! Should be fixed in the next build.

  • We plan to completely overhaul our markdown handling for the next major release, which will include both properly handling Lemmy's dialect quirks and integrating markdown editing tools into the composer.

  • Link

    App Store Connect reports there are a couple hundred empty spots, but we've had issues in the past with it reporting empty spots on the dev side but not letting more users join.

  • It wasn't, sorry about that! We've merged the fix for the next build, so hopefully that won't happen again.

  • You can show/hide read posts from the ellipsis menu in the top right of your Feeds tab.

  • Thanks for the bug report! We're looking into it.

    Does this happen on all sort modes, or only specific ones?

    Is it affected by toggling "show unread?"

  • Progressing well! We're hoping to have the next TestFlight build out soon.

  • This is one of Mlem's guiding principles! We strive to offer options to show as much--or as little--information as the user wants, with options to show/hide:

    • Author
    • Author instance
    • Community instance
    • Community subscription status
    • Thumbnails
    • Score
    • Display downvotes separately
    • Time posted
    • Saved status
    • Number of replies

    Plus a fully customizable interaction bar--and that's all just for posts.

    If you're on iOS, I'd encourage you to give us a try!

  • That's unfortunately not currently supported by the Lemmy backend. There is an issue open for it, though it doesn't appear particularly active right now.

    We have some major changes in development that might make this feasible to implement client-side--I've put up an issue for it, but can't make any promises pending a more thorough technical investigation.

  • This feature is in development for the upcoming Mlem 1.3 build.

  • Mark read on scroll is coming in the next build!

    As for searching within community, it's in the plans but I can't give a more precise delivery estimate.

  • Thanks for the bug report!

    I'm not able to reproduce this behavior--would you mind sharing:

    • Mlem version
    • iOS version
    • device
    • a comment that produces this behavior

    Thanks!

  • Thanks for the feedback! We'll take it under consideration.