There is no in-app option for this. However, iOS allows you to set accessibility settings on a per-app basis (System Settings -> Accessibility -> Per-App Settings), so you could use that to increase the font size :)
The indicator bar, everywhere, has indicators in the middle with buttons on the outside. The buttons look the same but slightly larger. If they are toggled on, then you can see them clearly as buttons. Making them look like buttons when they’re toggled off would help me parse the icon Mark Read is currently displaying, since it’s the action that will be applied not the current status of read/unread (how my brain is parsing it).
There’s now an option for this on the TestFlight beta version: Settings -> Accessibility -> Distinguish Interaction Bar.
If you go to the "messages" tab in the inbox, it should be there. If it isn't, you might need to turn off "unread only" by tapping the button in the top left of the screen. This isn't particularly obvious - we may improve this in future :)
When the inbox counter doesn’t go down, it’s nice to quickly know which posts aren’t correctly marked. I don’t think displaying that way makes it more clear but I am about to rush to do something so I might not be thinking it through. I’ll think as I use the app and get back to you.
Thanks, I appreciate it :)
I think another issue is that the client gets out of sync with the server on the Inbox page. I think it only notifies that a refresh is needed when new items are added to the list.
And when the refresh banner shows up, if you pull down to reload instead of pressing the button in the banner then a load indicator shows and eventually clears but the banner doesn’t. I’m not sure if that’s because the load isn’t happening, if it’s the load is being thrown away, of if the banner state isn’t being updated.
I'll look into these issues 👍
🤦♂️ I even noticed the link button was greyed out but for some reason I thought it was a bug and displaying as disabled even though it was clickable. Swapping from scroll to a hamburger menu is one way to handle future user stupidity but I’m not sure if it’s better, or there are better alternatives.
Yeah, this is a common cause of confusion; we really need to improve it somehow. A hamburger menu is an interesting idea 🤔 Another option would be to add some sort of arrow indicator to show that it's scrollable. I'll think about it 👍
Ah, I see! I get what you mean about the icons being confusing. Swapping them around might also be confusing, though... what about just always showing the "open envelope" icon, both when the button is on and when it is off? 🤔
The indicator bar, everywhere, has indicators in the middle with buttons on the outside. The buttons look the same but slightly larger. If they are toggled on, then you can see them clearly as buttons. Making them look like buttons when they’re toggled off would help me parse the icon Mark Read is currently displaying, since it’s the action that will be applied not the current status of read/unread (how my brain is parsing it).
Sure, I'll add a setting for this. If you're on the TestFlight beta, it'll probably be in this weekend's update.
For uploading an image, the bar I see above my keyboard is this, and I don’t see a place to change what’s in that bar.
If you put your finger on the bar and swipe to the left, it'll show more options :)
Voyager let you upload images for a comment. I’m not sure where they stored the images, but it would be nice to have the feature.
You can do this by tapping on the image button in the toolbar above the keyboard. You will need to scroll horizontally through the toolbar to see this option.
The inbox icons for read, unread look like indicators and then they are backwards.
Are you referring to this icon? This icon is for indicating read status:
They’re actually buttons indicating what will happen if you press them, but that doesn’t map immediately into my head.
The icon I circled isn't a tappable button; I'm confused :)
Mlem (App Store link) has all of the features you mentioned (I'm one of the developers).
To be able to see the different sidebars that are visible if you load these two sites (not only the side bar on server I’m registered to):
Go to the search tab and tap "instances", which allows you to read the sidebar of any instance. You can also search for an instance:
To be able to scroll these community (sorry not channel) lists separately and independent of channels from other servers (sorry not instances) (and not only the channels on server I’m registered to):
In the aforementioned instance page, there's a "communities" tab that shows this list:
Side note, if you are interested in hosting your own crawler instead of relying on https://data.lemmyverse.net/, you can fork my GitHub repo. It does the crawling as a free GitHub action.
Thanks, that’s super useful! We’ll have a look 👀 It would be great to not have to rely on third-party services like Lemmyverse that might go down for whatever reason
The tricky part is identifying whether a link is a theadiverse link or not. One solution would be to try the resolve_object request when the user taps on a link. If the request succeeds, open the link in-app. Otherwise, open the browser.
The downside of that approach is that there's a slight delay whenever you tap on a link while the app calls resolve_object. To avoid this, Mlem stores an array of all Lemmy/PieFed domains in memory. If the link's domain is in that array, we use resolve_object to open it in-app. Otherwise, we open it in the browser. We build the domain list from data obtained from https://data.lemmyverse.net/.
Another solution would be to look at the path of a link and see if it looks Lemmy-like. For instance, check whether it has /post as the first path component.
Neither of those solutions handle links that aren't from Lemmy/PieFed, which may still resolve with resolve_object. We decided that speed is more important that supporting those fringe cases.
For context, currently 97.5% of active iOS users are on iOS 18 or above, meaning that 97.5% of iOS users are able to use Mlem.
Supporting a version incurs an ongoing development cost for us. Changes we make have to be tested on more versions, and we're limited in which of Apple's APIs we can use. Dropping support for older versions allows us to focus our time on making Mlem the best it can be for the majority of users, as a modern iOS app.
With our current development capacity, it is not feasible for us to re-add support for iOS 17. You can find more details by reading our compatibility plan here.
Firstly, the Mlem app looks amazing and works brilliantly. Well done to all involved getting it to this point.
I'm glad you like it :) You're correct that Mlem doesn't include these features yet.
First is the ability to see the number of existing crossposts in the post feed.
This is tricky to implement at the moment - we'd need the Piefed developers to make some changes to make this easier for us. When we ask the PieFed server for a feed of posts, it doesn't tell us the crosspost count for each one. To get that information, we need to ask the PieFed server for each post's crosspost count individually, which is inefficient and difficult to manage. I'll raise an issue with the PieFed developers and see if this is something that can be improved upon 👍
Second is the ‘Notify about replies’ feature
This is high on the list of new features we'd like to add, but it will require quite a lot of code rewriting on our end so I can't make any promises on when this might be done. You could consider using Interstellar if this feature is highly important to you; according to this page Interstellar is currently the only app that can do this.
Thanks. I'm also getting this - it's probably due to the Cloudflare outage happening at the moment.