https://imgur.com/a/P7ZcVPO , can you give more info about your android version and device?
testAccount
joined 1 year ago
Can you give the steps to reproduce this, as I can't reproduce this problem rn.
We didn't actively impose this limit. I switched the image library that the ImageViewer uses. And that was its default zooming limit. I think its the same in other apps where they just keep it to the default settings.
Alright thats strange, in that version I added checks ("account verification checks") to ensure your account and device is in a proper state else it will give info to mitigate the problem. (To prevent external events, like when all the instances revoked the JWT when the hack happened and causing it to stop working for all the users) Here it fails on the first step. The first step checks if there any network capability. But from your screenshot I can clearly see you have wifi/mobile capability.
Could you give me some more information about your device/android version. In that version it now also requires the ACCESS_NETWORK_STATE permission for that check. Maybe you revoked it somehow?
The account is not ready yet msg is just that it hasnt cleared the checks yet. Maybe a better phrasing is in order but i am not sure what that is.
Yeah KBIN is getting the fundamentals right and at a pretty fast pace. I just don't like their nomenclature and techstack. It's also trying to be twitter and reddit at the same time.
Lemmy actually uses it own API, so you would think they would have documentation as a priority. Lemmy gets funded by NLnet (so is KBIN) and they get paid by each released feature. I think they focused too much on adding features, and this feature creep caused big performance issues. Aggregation is still big performance hog that causes instability which probably the biggest problem rn with Lemmy. They also wasted lots of resources into things that don't scale like the AsyncApi. Before they got hit by the reddit migration, they were even thinking of doing 1.0.0 release, that woulda complicated a lot of things. It's good that the migration happened, it shook Lemmy devs, probably would have been better if it happened earlier though.
What version are you using? 0.0.44 significantly increased the limit.
Their approach requires no additional work as it's fully automated. That's the biggest reason.
I wrote the routes manually which took some time. And it still needs quite some work for the summaries and descriptions
It still crashes in 0.0.42 ? In about section you can find the crash logs, can you send me that or make issue on GitHub with those logs?
Lemmy 18.3 added it html sanitation which doesn't seem to be properly configured
It's a bug introduced since lemmy 18.3. Update to 0.42 and it should be fixed
I fixed the problem already, dessalines just needs to cut a release
I tweaked it a bit, might resolve when ever 0.0.45 comes out