In iOS 26, there is a system-wide meaning to long pressing on the tab bar - it allows you to slide the selection bubble to a different tab. We decided to remove the long press gesture rather than override this system-wide behavior. We forgot to remove the setting associated with it, though; thanks for letting us know.
It would be nice to retain some way to switch to the most recent account quickly, though I'm not sure what the best way to do that would be 🤔 Open to ideas.
We feel that it’s better if your own profile appears exactly the same to you as it does to other users. Putting Saved in the profile might give the impression that everyone can see your saved posts, which isn’t the case.
In future, we also want to add post history, vote history and the uploaded images list. If all three were tabs in the profile, the tab picker would get super long and slow to navigate.
In the Search tab, there’s plenty of space to put all of those buttons without requiring the user to scroll through a picker. This is also where Apple puts the “Saved” list in some of their own apps (e.g. News), so putting it here makes it easier to find for users familiar with those apps.
I hope that makes sense. This is only on the TestFlight at the moment; we’re interested in what people think about this change so thanks for the feedback :)
Because you can see the same comment from many different Lemmy websites, there are many different links that point to the same comment. The website only accepts links from the same instance as the comment author.
On desktop, you can get this link by clicking this button:
Bu default, links copied within Mlem will be from your instance, not the author's instance. You can customize this behavior by going to the Settings tab -> Media & Links -> Share Links.
Selecting "original instance" will cause all links you copy to be the ones that Lemvotes requires.
I can't reproduce either of these issues at the moment. Could you provide us with some more info to help us track this down? It would be useful to know:
I did look into implementing something similar to this in the past, but there are some tricky UX problems associated with this design. Most prominently: if a user taps on a community link in a comment, what do we do? The intuitive option would be to slide a new page over both the sidebar and content panes, but unfortunately iOS only allows us to slide new pages over the rightmost pane. I might take a look at how Narwhal handles that 🤔
At the moment, we are focusing on implementing support for iOS 26, and following that we’ll be working on support for Lemmy 1.0. I’d love to revisit this at some point, but we can’t make any promises on when that might happen.
We’re open to contributions if anyone is interested in implementing something like this :)
Mlem dev here. Tagging is a feature implemented by Voyager and some other clients, Mlem doesn't have this feature. It isn't an official feature of Lemmy - clients store the tag information locally on-device rather than on the Lemmy server.
In Lemmy 1.0 (an upcoming version) they're adding support for adding notes to users, and Mlem will be adding support for it at that point.
I don’t have a need for v3, but I’d caution that you might do - v2 is missing quite a few features compared to v3. For example, Swagger v2 doesn’t support oneOf, allOf and anyOf. I believe you’re using some of those in the docs currently? I’d check but I’m not near a computer right now. I’m happy using v2 if you’re happy with it.
Edit: oops, typed some of the versions numbers the wrong way around. Apologies for any confusion
it's not really a current/reliable enough 'source of truth' to be feeding it into your codebase.
I’m auto-generating the code from the API docs, the same as @idunnololz is. As you say, it’s not really reliable at all. This is a major pain point for us at the moment.
For Lemmy we’re auto-generating our own source code from the Lemmy source code, which means that we can stay perfectly up-to-date with whatever Lemmy changes. Our script goes through the git history of the backend and finds when a certain feature was added to the API, then adds a comment in our source code explaining that. This saves us an enormous amount of time.
Unfortunately, the PieFed source code isn’t structured in a way that makes auto-generation feasible, so we use the API docs instead.
Because the API docs aren’t versioned and aren’t guaranteed to be correct, there’s a significant development overhead compared to Lemmy support. If there’s a new PieFed feature I want to support, I have to go digging through the PieFed git log to find which PieFed versions support it. I then have to comment my code manually to include that information.
In an ideal world, the PieFed docs would be kept perfectly up-to-date: whenever a change is made to the PieFed source, a matching change would be made to the docs at the same time. This would massively improve our development experience. It would also be great if the API docs repo had git tags for each PieFed version, so that we can traverse the git history in the same way we do for Lemmy.
I understand this may not be a reasonable request given how busy PieFed development is, but I thought I’d let you know what my pain points currently are and what could be done to alleviate them. I’m happy to keep doing it the way I am now, I just wish it was a little simpler to keep track of API changes :)
Feed/topic support would be fantastic. Community discovery is something that’s been lacking in Lemmy for a while, and I love PieFed’s topic implementation. I’d love to implement the topic list in the app I develop.
Worth noting is that Lemmy 1.0 includes multi-communities, which are analogous to PieFed feeds. I’m not sure whether you intend to maintain close parity with the Lemmy API going forward, or whether that was just to help apps onboard initially. Just thought I’d mention that they’ve got a series of API routes for it, in case parity is a consideration.
Heya! I develop Mlem along with @ericbandrews@lemmy.ml. The core PieFed features are now available on the beta version, and we’re currently working towards full parity with what we offer for Lemmy. We’re looking forward to bringing PieFed-exclusive features to our users once they become available through the API :)
I'm glad you like it :)
In iOS 26, there is a system-wide meaning to long pressing on the tab bar - it allows you to slide the selection bubble to a different tab. We decided to remove the long press gesture rather than override this system-wide behavior. We forgot to remove the setting associated with it, though; thanks for letting us know.
It would be nice to retain some way to switch to the most recent account quickly, though I'm not sure what the best way to do that would be 🤔 Open to ideas.