Turns out cloudflare was responsible for breaking the 206 range requests for lemmy.ca, and probably quite a few of these other broken sites too.
Here's how to fix with a caching rule:
this post was submitted on 25 Mar 2025
219 points (99.5% liked)
Voyager
6290 readers
28 users here now
The official lemmy community for Voyager, an open source, mobile-first client for lemmy.
Rules
- Be nice.
- lemmy.world instance policy
Sponsor development! π
π
founded 2 years ago
MODERATORS
Nice! I can verify it working too.
Imagine... infinite scrolling.
Imagine... never having to click Next.
The future is breathtaking! I'll be in my bunk.
Congrats, I just wish I could see everyone profile pics π
Thanks for that site for testing configuration for streaming video! Lemmy.NZ was failing but is fixed now.
In our case it was Cloudflare, I configured it to bypass the cache and it's resolved. Kinda defeats half the purpose of Cloudflare though haha so I will probably adjust it to do images but not video or something like that.
I pasted a specific screenshot elsewhere in this thread showing how to filter on just requests with a range header
Thanks! I have set ours up like that now too.
It seems Cloudflare should support range requests from the cache, but it might be a bit tricky to set up and perhaps not possible on a free plan. I read a bit about it but have given up for now.
Awesome, thanks so much for checking!
Regarding cloudflare, I know the lemmy.zip admin (@[email protected] was somehow able to get it working with caching, but I'm not sure how. I know the lemmy.world admins were having issues with it though and haven't been able to work around it yet. LMK if you do figure it out!
Thank you for your work on Voyager! The promo site looks great.
Thanks! π
I see gestures as one of the promoted features on that site. Is there a way to use gestures for navigation instead of actions? That is the one feature keeping me from Voyager. I want to be able to swipe to go back, etc., not swipe to upvote, etc.
You can go back by swiping from the edge of the screen. Itβs a gesture I use constantly.
Most or all of the other gestures can be disabled if you want.
Are you referring to the Android system navigation mode (Settings app > System > Gestures > Navigation mode)? I use 3-button navigation, because setting that to gesture navigation just causes too many problems in various apps.
But aside from that, my current Lemmy app, Thunder, allows me to swipe from anywhere onscreen to navigate back. Not just from the edge. Which is much better for accessibility purposes.
Iβm on iOS but, in voyagerβs settings, all the in-app gestures can be reconfigured or disabled. If you do that, then the native android or iOS gestures should work.
I think that is just one of the differences between the iOS and Android versions. I have all the gestures disabled in Voyager's settings, but swiping does nothing.
Let me get this straight. You've disabled gestures in Android to use the buttons, but also want gestures for Android inside the app instead of the gestures that the app provides and instead of using the back button that you just deliberately summoned for that purpose?
Okay it's possible. I think you'd need to disable the gestures in the app, and then find a way to customize the Android system gestures to work how you want them. That is phone dependent.
But. To be brutally honest: Learn to use the system edge gestures. It takes a day or two to get used to, but then you'll never miss the buttons or get frustrated with apps that work as intended ny default. Surely this must also be an issue in all other apps that use on screen gestures.
Close.
- Android gesture navigation replaces the system back button with a swipe from the edge of the screen. This in itself causes an issue with apps that (since long before gesture navigation was introduced to Android) use an edge swipe gesture to activate an in-app feature. The first app that comes to mind as an example is Termux. Swiping in from the edge of the screen opens the side menu in the app. But with gesture navigation enabled, this same edge gesture instead triggers the system back button, closing the app. I have seen some third party Android skins offer an option to only trigger the back gesture when swiping from the bottom 50% of a side edge. In the case of Termux, swiping from the top 50% would then open the menu as expected. Alas, GrapheneOS does not have this option.
- Aside from this intrinsic issue, I also experience bugs in certain apps that are resolved by switching to 3-button navigation. From what I can tell, this might be fixed by these apps implementing newer/different Android APIs or something. I don't know. I'm not an Android developer.
- Even with the previous issues resolved, system gesture navigation is all about swiping from the edge of the screen. What I want (and Thunder provides) is the ability to swipe from anywhere onscreen in order to go back. Sort of like swiping away a card. This is a behaviour that is only implemented at the app level.
Should be... Although, I believe on Android + system 3 button nav + android specific voyager theme, it doesn't have navigation swipes. the iOS theme should. There might be a way to get it working, I'd have to check
Neat, it does work if I switch to the Apple theme! One criticism that I still have about it is that it only works when swiping from within the left 10% or so of the display. Which I assume is by design. It would be nice for the user to be able configure that threshold up to at least 50%.
Wow this is great and i love the new domain name
The promo website looks really fancy!
Nice! This is great.
Having the screencaps on a shareable page is far better than me trying to explain what Lemmy is or how it functions.
Well done!
curl -I https://swg-empire.de/pictrs/image/c6d5a936-1566-4154-947d-8926fbe07fe5.jpeg
Hmm, my pictrs doesn't seem to like HEAD requests. From what I can see every service is configured correctly. Apache is forwarding it correctly to Nginx and Nginx is using the latest configuration from ansible.
But my pictrs does support ranges so I guess everything is ok.
It looks like it is working great through my test tool! thank you!