this post was submitted on 27 Jan 2026
7 points (100.0% liked)
Mlem for Lemmy
6784 readers
2 users here now
Official community for Mlem, a free and open-source iOS Lemmy client.
Rules
- Keep it civil.
- This is a forum for discussion about Mlem. We welcome a degree of general chatter, but anything not related to Mlem may be removed at moderator discretion. This is not a forum for iPhone/Android debate. Posts and comments saying nothing but "iOS bad/I use Android" will be removed as off-topic.
- We welcome constructive criticism, but ask that it be both precise and polite.
FAQ
- When will insert feature here be implemented?
- Check our issue board--if there isn't an issue open for the feature you want, feel free to open an issue or make post! Just remember that devs are people too--we're doing this for free in our spare time, and building a quality app takes a lot of patient work.
- Is Mlem available for Android?
- No. Mlem is written using SwiftUI, which is not currently supported on Android. If such support becomes available, we will look into bringing Mlem to our Android friends.
- How do I join the beta?
- How do I join the dev team?
- Head over to our recruitment channel, or go straight to our GitHub and read CONTRIBUTING.md to get started.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
@blaze@piefed.zip has been asking for this feature for ages and @Skavau@piefed.social made an issue for it on the codeberg already. The reason this isn't in the api yet is because it isn't anywhere in piefed yet. AFAIK, the read/unread status of comments isn't currently tracked anywhere within piefed. Additionally, for this feature, I don't believe we track the timestamp at which you do interact with a post...so doing something like calculating the number of new comments that have occurred since you last opened that post isn't possible...yet.
I don't have a great idea of how to do this in a db-efficient way. Keeping track of when every user opens each post sounds like db-query hell. However, there might be clever caching tricks to make it a bit less computationally intense. @rimu@piefed.social would likely have a better idea of how to do this.
Thanks for the info :) Lemmy 1.0 tracks a
readAttimestamp; maybe it's worth looking at how they're doing it.