Thanks! I totally fell for the “crosspost” label—I didn’t realize Lemmy just uses that term to mean “posts with the same link.”

The merged crossposts feature we have planned is actually exactly what you’re asking for then, since that’s what Lemmy means by a crosspost.

Do you have an example of a post where lemmy-ui does this? I’d love to look into how they implement it but I can’t find an example of the feature in action.

Mlem dev here.

This feature, as suggested, presents a fundamental technical problem: frontend clients load posts a page at a time, and so are only aware of the posts you’ve already scrolled past and the ~20-50 posts ahead in the feed. It’s therefore not possible to find all posts with the same URL and aggregate their comments into a single chain under the first occurrence of the URL, at least not without loading infeasible amounts of data ahead of time.

We do have a merged crossposts feature planned, which achieves the same basic functionality but using the backend crosspost data rather than absolute URLs; our comments view also currently shows the list of crossposts and indicates the number of comments on each one.

Alternatively, a filter that only shows posts with comments

That’s a good idea, we’ll add it to a future build.

Mlem has this feature planned–we have a clear path towards implementation, but there’s a lot of groundwork and design to do first so it probably won’t be delivered for at least several months.

This is one of Mlem’s guiding principles! We strive to offer options to show as much–or as little–information as the user wants, with options to show/hide:

• Author
• Author instance
• Community instance
• Community subscription status
• Thumbnails
• Score
• Display downvotes separately
• Time posted
• Saved status
• Number of replies

Plus a fully customizable interaction bar–and that’s all just for posts.

If you’re on iOS, I’d encourage you to give us a try!

This feature is in development for the upcoming Mlem 1.3 build.

Mlem is fully FOSS!

GitHub

App Store

❤️

We’ve got that feature in testing right now, we’re hoping to have it out to the App Store in the next couple days!

Mlem is SwiftUI and FOSS! I know there are some issues with the current App Store build (weeps in janky scrolling) but we’ve got a major update hitting beta tomorrow and the App Store as soon as Apple will allow that’s going to fix it.

Well this article just isn’t right at all

I drive an entry level EV (Hyundai Kona) that advertises 4mi/kWh, which is roughly accurate (2-3 in the winter, 5-7 in the summer). That’s 25 kWh for 100 miles.

Average cost of electricity in the US is, according to a quick Google, somewhere between $.15 and $.25 per kWh; where I live it’s a steeper $.33.

Therefore, depending on where I charge, I’m paying anywhere between $3.75 and $8.25 to drive 100 miles–$1.50 short of the article’s published $9.78 even with my expensive power.

In reality, though, I pay nothing–my office offers free charging. Show me an office with free gas.

Good news–we decided that “some support is better than none,” and quietly released the iPad app to the App Store as well. It’s not perfect–we’re pretty heavily leaning on SwiftUI’s automagic cross-platform–and while we finish filling out our core features it’s not going to get much dev time, but come 1.2 we’ll make it all nice and shiny

Funny you should mention that, I’m actually working on implementing that exact feature right now! It’ll be out in the next build.

Thanks for the download, and I hope you enjoy it! We’re firm believers in the native Swift experience, even though it takes a little longer to develop in

It’s coming! We’ve got development slated to start early August, it should enter TestFlight beta sometime shortly after then.

Mlem dev here—couldn’t agree more about Gavin, he’s a fantastic guy. Gave us some helpful tips about getting through App Store review. Massive props to him for getting that app up and running so fast.