Ah i see. Ill add it to the roadmap

I already submitted a fix. Hope it goes through.

Urg, my submission to the play store got rejected. I’m going to need to make some modifications to the release to get comply with app store policies.

It looks like some of the optimizations I did broke custom post feed actions which is likely what you are crashing from. I’m going to release another hotfix in a few minutes.

A fix is on the way.

Summit will not allow me to post URLs or images.

No matter the image, URL, post, instance, etc.

Thanks for reporting. Looking now.

Added to the roadmap.

This feels more like a feature that the Lemmy server should implemented. At best the client can provide the information, but I think having Summit enforce post limits would be a terrible idea.

As for showing some sort of infographic for post frequency, I can’t immediately think of any way to implement this without it feeling a bit naggy/annoying to the end user. With Summit’s focus on configurability, I’m sure users will want to be able to turn such a feature off and if all the heavy posters simply turn it off then I don’t feel like it would be worth implementing.

I’m going to veto this idea for now unless someone can come up with a better way to implement this.

Thanks!

There are a lot of toolbars in the app, which toolbar are you talking about?

Gotta be 200. This is a huge change and not a decision to be made lightly.

Ah, this is a bug with Summit.

The change is, before this release Summit would insert a markdown link to a person/community when a mention suggestion is tapped. After the change Summit will instead insert a Lemmy specific mention when a mention suggestion is tapped.

The inserted text itself is different but the actual difference is they use different mechanisms to mention a user. The old way inserts a hard link which would link to the instant the user is on. The new way inserts a mention, it relies on Lemmy to generate an appropriate link based on the instance you are currently on.

In other words the old method inserted an absolute link (ie. Everyone will be directed to the same page no matter which instance they are on) where as the new method is relative (users are directed to a different page based on which instance they are on).

I honestly don’t know lol. I mostly just want to poll Summit users if at all possible. In an ideal world I would have implemented this poll in app but I don’t have a mechanism like that (yet).

I thought I fixed this, but apparently not. Thanks for reporting. I’ll take another stab at it in the next release.

Figured out the cause. I’ll issue a hot fix for it.

Hmm i can’t reproduce this on my end, even if I use an account on your instance. I’ll check if the crash is logged later tonight.

I might have filled in some form wrong. I’ll check tonight. Thanks for flagging!

I had an aluminum can explode the same way.

more like me when i get woken up by a loud bang sound from the kitchen.

biweekly, bimonthly, etc.

Wtf does it mean? Twice a week? Every two weeks? Who knows. What’s the point of this word when it’s so ambiguous.