> polish
> looks inside
> text portion of the post is in english
this post was submitted on 25 Aug 2025
57 points (98.3% liked)
Summit
1129 readers
17 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.
Enjoy your well deserved vacation!
The material 3 experience is amazing so far. Great job!
Thanks!
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.
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.
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