this post was submitted on 24 Mar 2025
18 points (100.0% liked)

Summit

887 readers
7 users here now

Community to discuss Summit, a Lemmy reader for Android.

App (Play Store): https://play.google.com/store/apps/details?id=com.idunnololz.summit

APK: https://github.com/idunnololz/summit-for-lemmy/releases

Support the app

Support me on Patreon

Website: https://summit.idunnololz.com/

founded 2 years ago
MODERATORS
[email protected]
18
List of requests (lemmy.asudox.dev)
submitted 1 week ago* (last edited 1 week ago) by [email protected] to c/[email protected]
9 comments fedilink hide all child comments
 

Here are a few features that I think would be good to add:

Administration & Moderation

  • Signup applications (under the Reports button in Inbox would be ideal)
  • View votes (afaik mods should also be able to view votes in their communities)
  • Perhaps some sort of administration panel
  • Merge "Admin tools" and "Mod tools"
  • View moderation & report history for users
  • Better modlog UI
  • Checks for whether or not some mod actions can be done on a user and hide options that can't be applied
  • Add "Feature Post in instance" to posts

Create new post dialog

  • Rename "Compose post" to "Body" or "Text"
  • Pre-expand text field area
  • Add new field for thumbnail URL
  • Allow choosing post language

Create new comment dialog

  • Allow choosing comment language
  • See who you are replying to in addition to the comment content

Media

  • View & manage uploaded media
  • Add option to loop videos
  • Add option to unblur NSFW images when in NSFW communities

Other

  • More user friendly errors
  • Advanced search (search in community, filters, etc.)

Oh and the updated join-lemmy.org applications page lists that Summit has 2 GitHub repos. I think it would be less confusing to just link to the repo that contains the source code instead.

top 9 comments
sorted by: hot top controversial new old
[–] [email protected] 3 points 1 week ago* (last edited 1 week ago) (3 children)

To simplify these requests I will group all of the moderation requests together in the roadmap.

Rename “Compose post” to “Body” or “Text”

Will be in the next release.

See who you are replying to in addition to the comment content

This is already a feature in the app technically. In the create comment screen tap the three dots button (top right) > Show full context.

More user friendly errors

Too vague to action on as-is.

Advanced search (search in community, filters, etc.)

This is already supported. Tap Search in the nav bar > Tap the search field > Tap either "Filter by community" or "Filter by creator".

Everything else has been added to the roadmap.

[–] Flagstaff 2 points 6 days ago* (last edited 6 days ago) (1 children)

Too vague to action on as-is.

Maybe I can elaborate on @asudox's note:

Client error. Code: 401. Message: Attempted to call an auth'd endpoint with the wrong account. Account instance: (one instance URL) Api instance: (other instance URL).

When I went to this post, initially, after having changed accounts across instances in the app, it didn't give me the instances-mismatch prompt at the top even after refreshing, and then I couldn't comment. This happened with multiple posts and I haven't able to figure out how to get it to change APIs at the moment of account-switching. For example, the Lemmy app Thunder has no such issue; it always uses the correct API per account.

[–] [email protected] 2 points 5 days ago (1 children)

Could you please provide some reproduction steps for this issue? I cannot reproduce it with how I am testing the app.

[–] Flagstaff 1 points 1 day ago

I ultimately couldn't replicate it, but there was a weird time just a few hours ago when I was in one account and literally everything I opened in the feed opened in the other one, which then kept yielding this desync error so I couldn't comment (even after ). I'll see what I can do to reproduce it...

[–] Flagstaff 2 points 6 days ago* (last edited 6 days ago) (1 children)

Tap Search in the nav bar > Tap the search field

Could there be a setting added to automatically open the keyboard immediately on this first tap, which is how comment-searching already works? Search currently feels like the new/worse Play Store, which makes you have to tap the magnifying glass at the bottom, and then the text field at the top, which seems counterintuitive. Thanks!

Additionally:

  1. Open this post
  2. Do a general search, for example to try to retrieve a link from elsewhere on Lemmy to comment into this post (which means you have to back out of this post first, which is not good)
  3. Try to return to this post

I have to manually look for it again the way I found it the first time instead of just being able to press Back or any faster way to return to it.

~~There is no localized view history or something like that.~~ The way other apps do it is by allowing the general search to be accessible from a side pane or 3-dot menu at all times.

Update: Okay, I found History. Wow, the settings are deep!

[–] [email protected] 2 points 5 days ago (1 children)

Regarding the search screen: There is a feature request on the roadmap to make double tapping search on the bottom bar open the search screen with search focused.

This could solve this issue but it's not perfect since the gesture is random and doesn't really follow any existing UX design. By the way the reason why search looks the way it does is because I received feedback that some people wanted to be able to view their communities with a single tap of a button and when not on the home screen. The search screen has turned into a general hub of random lists as a result of that request.

For being able to search from a post, there isn't technically anything preventing this from being supported in the app. I just think it's a not something the average user would use. As a solution I can add a setting that shows the bottom bar even on the post screen. I'll add this to the roadmap but let me know if you don't like this idea.

[–] Flagstaff 1 points 5 days ago (1 children)

The option for a persistent bottom bar would be fine, yeah! An option to immediately show the keyboard or not when calling the search engine might be nice as well and would solve this issue without disgruntling the users you reference.

[–] [email protected] 2 points 2 days ago

Sure i can add that to the roadmap.

[–] [email protected] 2 points 1 week ago

Thanks for the info