> polish
> looks inside
> text portion of the post is in english
this post was submitted on 25 Aug 2025
65 points (97.1% liked)
Summit
1148 readers
14 users here now
Community to discuss Summit, an open-source 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
Source: https://github.com/idunnololz/summit
Support the app
Website: https://summit.idunnololz.com/
founded 2 years ago
MODERATORS
🇵🇱
Poland mentioned
Impressive
Most impressive.
But, you are not a Jedi yet.
I'm so glad I came across summit. You're the best!
Looks great and seems much more responsive, but I appear to have lost upvote count on posts.
They show up for comments though.
Pushed a release out to fix this. Should be available in a bit.
Working! You're amazing, as always! Thank you for all the updates.
Great update, tho for me the downvotes button seems to have disappeared in my post feed and I couldn't find the option to re-enable it
Looking into this tonight.
Thank you so much (like in general and your quick responses)! Don't stress though it was in no way a demand, more of an FYI
Would you consider an option for the "Link actions" menu to have plain text preview? I find it better than the preview link action(extra click, the request).
Jerboa:
Sorry, I don't think I understand the feature request. Could you please give more details?
From the screenshot it looks like you prefer Japanese. If you want you can write your comment in Japanese. My partner is fluent and he can translate for me :D
As shown in the screenshot, the initial menu has the link's("@vanessafoley") address at the top. In Summit you get the actions list, then you need to pick "preview link" to check the address(which also has an actual preview of the website, which i prefer to avoid).
Or of course just copy and paste somewhere :)
Oh I see. I'll add this to the roadmap.
Fix a bug where the upvote or sometimes downvote button was missing
I can confirm that this bug is still present on v1.71.4 (289). Rebooting my phone seems to fix it, but only temporarily.
I havent seen this bug in a while personally so I think this is likely related to the combination of settings. Can you please dm me your settings. You can send me your settting by going to Settings > Import & export settings > Export settings > Copy to clipboard. You can unchckec "include database" as i dont think its relevant and will make the test too long to paste.
Settings sent! Thank you for looking into this! Let me know if there are any other data which might be useful.
I tested your config for about an hour but I was unable to reproduce the bug. There must be some specific thing/action that is triggering the bug. Do you notice any patterns to when the button disappears? Like maybe after performing certain actions or leaving the app for a while and coming back?
Thanks for spending your time on this.
Do you notice any patterns to when the button disappears? Like maybe after performing certain actions or leaving the app for a while and coming back?
I haven't identified a reliable sequence of actions which reproduce the bug every time, but it happened twice today, and I tried to take note of some details.
Both cases occurred after I closed and reopened the app after encountering some other strange behaviour.
Case 1
Was reading this post: https://sh.itjust.works/post/46917320
Followed link to this post: https://lemmyverse.link/lemmy.world/post/11959030
Finished reading, clicked back and returned to original post.
Tried to upvote a comment, button unresponsive. Refreshed the post page, tried to upvote again, no change.
Closed and reopened the app. No downvote buttons.
Case 2
Clicked on this post: https://sh.itjust.works/post/45340057
Tried to scroll down to read the comments, and the app froze.
Closed and reopened the app. No downvote buttons.
I realize this isn't much to go on, but I thought I'd send this along just in case.
Does this help narrow down the issue at all?
Is there any other info I should take note of which might be helpful?
Cool. I figured out the cause and will have a fix in the next release. By default, the app tries to determine if a URL is a Lemmy instance or a regular website. It does this by pinging a specific Lemmy endpoint. if it returns success then it's a Lemmy site, if it errors for some reason then the app will try to hit the main webpage. If it works then the app assumes that the URL is a website but not a Lemmy instance. In this case, the app will auto-assume all Lemmy features are disabled, including downvotes.
Lemmy servers are generally not that stable compared to more commercial servers and it's also possible that a phone's connection can become unstable. In these cases what could happen is that the Lemmy API instance check errors due to either timing out or the server returning an error and then the fetch on the front page succeeds. When this apps the app assumes the instance is not a Lemmy server and disables all features causing the downvote button to disappear. Restarting the app fixes it because it causes the app to re-check the server to determine its capabilities.
A simple fix for this is for the app to simply cache server capabilities and fallback on the cached information if an error occurs while re-evaluating the server's capabilities.
That might not have been the only cause, as the downvote buttons just disappeared on v1.71.6.
I was swiping through posts, came to this one, and opened the link in Firefox.
Copied a quote from the article, switched back to Summit, and started writing a comment. Switched to Firefox to copy a second quote, then switched back to Summit.
Upon returning to Summit, the app seemed to "reset itself" to an extent, kicking me out of the post and comment composition, back into the main feed, which refreshed itself.
This doesn't seem to be related to if a URL is a Lemmy instance or not.
Could there be some sort of memory leak which gets triggered if someone swipes through too many posts or something? Just spitballing here, I don't really know anything about app design.
Any other info which would be helpful?
Enjoy your well deserved vacation!
Thank you! So extremely busy before vacation though with life stuff :(
The material 3 experience is amazing so far. Great job!
Thanks!
Downvote button completely disappears sometimes
Can you consistently reproduce this issue?
Unfortunately not. I've tried clearing the cache and force-stopping the app, it worked once but then never more
Rebooting my phone seemed to fix the issue for me.
Edit: But only temporarily.
Fix a bug where posts are incorrectly marked as read when "Swipe between posts" is enabled.
I'm on 1.71.3 (version code 288), and I think this bug is still present.
After entering and exiting a post in the feed, everything looks fine at first, but when I refresh the feed, the posts on either side are incorrectly marked as read.
Edit: Now it seems that the bug is gone, despite no change in the version number. Very strange...
Let me know if it comes back.
It has come back. Not sure what triggers it.
The newly released .4 doesn't seem to have had it's version number increased. I've installed it, but obtainium kept telling me there's an update. Manually updating directly from GitHub also didn't change the version number from .3.
I didn't commit my changes onto github. I only committed my version bump 🤦. Just committed my changes now. Update should be available in ~30minutes.
Yup that seems to have worked, thanks!
I'm not sure if I should call that a bug or not: I often browse with "hide read" enabled, and I also have "mark cross posts as read" enabled. When scrolling the feed and encountering a cross post, it's correctly married as read, but apparently that happens after the step where posts are hidden, so it isn't actually hidden. Would be nice if that could be included in the hiding of posts.
I'm not sure if I should call that a bug or not
Which item are you referring to?
Well the stuff I wrote in the comment. Not really related to any point?
I had to go back to 1.70.1 after the update any post I try to open app crashes immediately. I can send you logs if you want
Pushed a release out to fix this. Should be available in a bit.
Some images don't seem to load for me, is anyone else getting this problem? Tested in Interstellar and it displays fine. Example: https://fedia.io/m/gems/t/2625829
When i visit your link it asks me to log in. Are you logged into fedia.io when you view the link?
It's a thread at !gems@fedia.io but strangely enough it does load now for me (it was a GIF). However, other images aren't loading for me either sometimes.
Oh damn, thats a cool community. Sorry for the late reply but are you still getting this issue? I checked the community and I am unable yo reproduce the issue myself.
No worries, I know you're busy. Still having the same issue, example:
Not to step on anyone’s toes, but HTTP 4xx errors usually mean the request isn’t allowed or can’t be fulfilled on the client side (like needing to log in, an expired link, or access restrictions). 5xx errors are the ones that point to real server issues. So in this case it might just be the hosting platform enforcing access rules rather than a problem with Summit itself. Just sharing a thought.
Network edge cases — interrupted or partial requests can reach the server in an incomplete form, which results in 400.
Edit/afterthought:
Something that occurred to me afterwards: sometimes 400s can also pop up from network edge cases — like an interrupted or partial request reaching the server in an incomplete form (RFC 7231 §6.5.1). And since you’re on a different Lemmy instance, it could just be that side acting up. Lemmy servers typically run behind an nginx reverse proxy (default setup), and if that proxy or backend gets overloaded, it may return 400s. Add in federation quirks like sync or backlog delays, and it would explain why it sometimes works fine and sometimes doesn’t — different people see different images fail at different times.