Are you a doctor??
Connect for Lemmy App
A community for the mobile app Connect for Lemmy.
Links
My phone's image editing app is crap
:P 'Tis but a joke.
I've added an option under settings (as of 1.0.81) to turn off Image Preloading which should help a bit. Part of the problem is that the files Lemmy serves as a 'thumbnail url' are actually the full sized image and the only resize option available to developers is specifying a thumbnail resize value which resizes it with raw pixel sampling so it can look pretty pixelated.
You are awesome.
Thanks I will take a look! 2 questions:Which post view are you using? Asking because the list views load only thumbnails whereas full width is the full image. And which version is this? Asking because some improvements were made if you're on the beta.
Not the OP but ive noticed the same issue. Im using List view and I think its version 1.0.68. Hope this helps, Im loving the app so far though!
I'm using list view as well.
Reversed list.
Can you check if you still see this issue on the latest beta version (1.0.82)?
I'm at my data limit so I can't. Sorry
I think it's because there are a lot of meme posts on my front page (my default frontpage is to display all communities). I changed the frontpage to subscribed community, I hope this will reduce my data usage
I'm assuming the increased data usage comes from fetching the content directly from the source where large images or videos might be allowed, whereas on Reddit this stuff was compressed and had limited sizes
I'm at 56g for connect (+9g for Lemmy and +35g for boost) in the same time period. The last time period had me at 81g for boost, so I am fairly sure I am the problem in my case 😅
I see the same problem on other lemmy apps, I think the problem is not the apps but large image size
I used Boost when I was viewing reddit content. Average usage per week was ~9 GB. I switched, completely, to Connect 3 weeks ago. Average usage per week has been ~6 GB. I don't know how to factor in time of usage to create a unitized data/time metric, but I think you have a similar issue in your reporting. TL;DR No obvious/realistic impacts to data consumption; additional data logging required to quantity appropriately.
If this big issue could be fixed, I could see myself using this as my main app!