This release is be focused on polishing the app further.
I've been extremely busy for the past few months and will continue to be busy for the foreseeable future. To help get changes out sooner, this release will be broken down into multiple parts.
Full changelog
- Start migration to Material 3 Expressive, Google's new design system.
- Improve app startup time.
- Improve experience for instances that disable downvotes. Downvote buttons are hidden on the post feed/post screen. Downvote actions on these instances are ignored.
- Improve search support on PieFed instances.
- Improve the feel of bottom sheet menus. Fix a bug where flinging on a bottom sheet does not dismiss the bottom sheet.
- Fix a bug where the wrong image is shown in the post feed.
- Fix a bug where tapping on retry on the load error UI on the search screen will add another load error UI.
- Fix a bug where sometimes the app says there is a network error even though there is an internet connection.
- Fix a bug where the app cannot recover from a network error until the app is restarted.
- Fix some bugs related to "Find in page".
Update
Added more minor changes as part of the v1.71.2 release:
- Fix a bug where the upvote or sometimes downvote button was missing.
- Improve gestures so that the gesture icon is always on screen. This fixes the issue where the gesture icon might be off screen if the post/comment being acted on it very long.
- Improve comment/post editor so that the view will auto scroll to the cursor when the keyboard is opened/closed. This fixes an issue where opening the keyboard would cause the cursor to become offscreen.
Update 2
- Fix a bug where posts are incorrectly marked as read when "Swipe between posts" is enabled.
- Fix a UI bug where reporting on posts will show the progress spinner forever.
- Minor tweaks to post UI.
- Update "Manage internal settings backup" UI.
- Add setting to mark post as read on post hide.
- Add search option to the "more" menu on the community feed screen. Tapping it will open the search page. If tapped within a community feed, the community filter will be auto-set to the correct community.
Update 3
Release changes as v1.71.3. Still super busy so expect slower than usual updates. Going on vacation in 2 weeks. Need to get a bunch of home stuff done and also really busy at work :S
Update 4
Overhauled the paging logic for those who prefer to not use infinite scrolling. The paging code is out of date and it has not been maintained well. This overhaul should fix a lot of bugs. I will also be dogfooding the app with no infinite scrolling for the next couple of days just to make sure all major bugs are resolved.
- Overhauled the app's paging system which is used when infinite scrolling is off.
- Fix a bug where posts with an embedded video link would show only the video and nothing else (eg. no text or URL even if the post has them)
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.