Skip Navigation

User banner
Posts
61
Comments
250
Joined
2 yr. ago

  • It's the same link as before--the beta is full, so if you're not in it you'll just have to wait for the App Store build :(

  • Sorry we've been so slow getting around to this one--we've got a lot of bugs to squash and this one got a little lost! I'm looking into it now, hoping to have it fixed in the next build.

  • You're supposed to be able to drag and drop from the tray to the bar--if that's not working, please send us a screen recording so we can figure out what's broken!

  • Thanks for the bug report, and I'm glad to hear it's running smoothly!

  • No worries! This has definitely been the longest span between TF builds.

    By the way, I've gone and deleted all the posts that weren't unpinning properly--are they still showing up for you, or has that fixed it? There should just be the 1.0.1 announcement pinned and nothing else

  • We're currently elbows deep a backend overhaul that should smooth out a ton of weird little state issues (things like the saved button "flickering" and interactions waiting on network round trip to apply). This touches so much of the app that shipping a TF now would turn up a ton of stale-on-arrival bugs, so we've been holding off shipping a TF until we get that merged.

    By the same token, we're targeting a TF build more or less the moment that drops--the PR is https://github.com/mlemgroup/mlem/pull/556 and it just entered draft yesterday, so I'm hoping to have it in by the end of the week.

    Re: pinned posts, that's an instance sync issue as far as I can tell--they're not pinned on .ml, but we've heard similar reports from beehaw users.

  • That's been on our issue tracker for a little while, I'm pleased to report we merged the option to partially or fully disable haptics into the dev build last week so it'll definitely be included in the next public build

  • We've got that one in development, it should be out in the next TestFlight

  • We've got it on our issue tracker--it's slated for 1.2, which should be soon-ish (dev resources are a little scant right now since day jobs are getting busy)

  • Oh yeah, whoops! Bumped the build, it should be the same in both now.

    Normally the deployment strategy is to merge the TestFlight tagged code into master once we're ready to submit, then rebuild from master and submit that build--it's a "different build" but the exact same code. This time we ran into some Apple Review snags (they wanted a way to permanently delete your Lemmy account from within the app), so we had to hotfix that on master and forgot to release that to back to the TestFlight.

  • We've got an issue open for it, should be out in the next build. Chances are we're just going to implement what Apollo did and Memmy currently does where link thumbnails get a little icon overlay, but we're always open to new ideas if anybody has them

  • I believe this comment is referring specifically to thumbnails in compact and headline mode--large posts already distinguish between images and links by embedding the link preview in a complex with the url and website icon.

  • There's a fix for that coming out in the next build, but we can definitely make it toggleable too

  • Thanks!

    GitHub issues are preferred because then they're on our issue list until they're either rejected or implemented. I do my best to put feature requests from the community on the issue board, but I do miss a few here and there.

  • We're playing around with some ways to handle this right now--the two main options are:

    • Downsize tall images to fit in the max height (this is the most promising one, since ~95% of truncated images only get very slightly downsized)
    • Just show the whole image, who cares if it takes up five screens (easier to implement but makes tall images a pain to scroll past)

    Chances are we'll just end up with a toggle between the two though lol

  • Yes! We're currently working on a robust middleware system that will, among other things, let us elegantly handle multiple APIs

  • There are! We haven't implemented it yet out of concerns around API etiquette--there is no batch mark read endpoint yet, so it's kind of a "scroll fast to spam server" feature and we really don't want to build something that's harmful to the Lemmy ecosystem. We'll run some numbers and reach out to a couple admins, see what their sense of the impact might be, and proceed from there.

    Lemmy does have rate limiters, so it's probably fine, but it's still something we want to make sure isn't going to be a headache for instance owners, especially small ones.

  • We've heard this from a small percentage of users in the TestFlight--we're still trying to determine what's triggering it. Would you mind taking a screen recording and sharing what model/year of phone you're on? You can also message me directly if you don't want to put it in a comment