Mlem dev here. We aren’t associated with the Lemmy developers :) We set up !mlemapp@lemmy.ml shortly after the Reddit API Exodus, and chose to host our community on .ml because it advertised itself as a FOSS-centered instance. We’ve considered moving to a self-hosted instance but haven’t got around to it yet.

It’s not real.

This is a joke referencing similar tweets he’s made in the past, such as this one:

https://xcancel.com/Cobratate/status/1783049915800736108

On Mlem, long-press on a post then tap “Share…” -> “Crosspost”

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.

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 :)

You’re welcome :)

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:

To be able to search “ask lemmy.ml” filtered by communities and see “https://lemmy.ml/c/asklemmy” show up in some way.

You can filter by a particular instance in the community search. Here, filtering by lemmy.ml and searching “ask” surfaces asklemmy@lemmy.ml:

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

Mlem dev here. You can use Lemmy’s resolve_object endpoint to get the data for an entity given a URL pointing to it.

For example, here’s the request for this post: https://lemmy.world/api/v3/resolve_object?q=https%3A%2F%2Flemmy.ml%2Fpost%2F37416479

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.

Mlem dev here. Thank you, that was the issue on our side too 🙃

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.

There’s a button for it in the toolbar above the keyboard. You need to scroll horizontally on the toolbar to see the button.

Should be fixed now.

Thanks, we’ll be keeping an eye on this 👀

Mlem dev here. Mlem has some logic that looks through the community/instance description, and tries to extract the rules list. If it’s able to find the rules, it displays them as options in the report sheet:

At the moment, Mlem fails to recognize the formatting that lemy.lol uses. I’ve added a fix for this, so it’ll work properly for lemy.lol in the next version. The “he’s just a chill guy” image was confusing our parsing logic :)

It would be nice if there was a standardized way to do this, I agree. Reddit gave communities a dedicated “rules list” field, separate from the description field, which would have made this easier.

Mlem dev here. If you get a popup saying “Image too large”, this is because your instance has imposed a maximum file size on uploads. Different instances choose to have different limits. Consider sharing the image via another image service (https://catbox.moe/ is pretty popular on Lemmy).

If it’s the bug where the submit button is greyed out, you can work around it by adding a space to the title and then removing it again. That issue is fixed in the beta :)