Lemmy is planning on having its 0.18.0 release tomorrow, and this adds compatibility for it.
Just a little feedback since updating to the latest Jerboa version… Loading & scrolling is super smooth!, & no error messages, at least so far…really nice update… 2 things though, the default listing type & sort type are displayed as Local/active, ignoring my defaults in settings… Secondly, read items in the inbox, are displayed, even when set to show unread only… Pretty minor, I know, but just noticeable given this wasn’t the case before the update… Thanks all👍🏼
My vlemmy account is not working on Jerboa. :( But my nsfw account is.
Woooooo comment sorting!!! (And other great things I’m sure, but) HORRAY COMMENT SORTING!!!
I am seriously impressed by the number of fixes in this release, including a few I was hoping for. It can’t show up in fdroid soon enough! Thanks to all the contributors!
Anyone else having issues to see nsfw with this release? Was unblurred before and blurred now with no change in my setting and all seems correctly checked… As usual asking for a friend 😋
Well afaik it always should have been blurried without an option to disable it
Will this one get pushed to the playstore? or do I need to side load it like i have for 0.34?
Highly recommend using f-droid and adding the izzyondroid repo tho. That’s where updates will get fastest.
In my f-droid the latest version is .33 somehow
The Google Play Store version crashed instantly on launch after flashing up the changelog (mentioning v0.0.35) but looking at app info it said version 0.0.33 so maybe the play store hadn’t rolled out the latest build. Installed the GitHub release apk instead and had no issues.
We’ve upgraded lemmy.ml to use the new
0.18.0back-end, so it was crucial that I got this jerboa release out ASAP to be compatible with it.We’ll have the official release of
0.18.0tomorrow.Will there be an arm64 docker image so I can upgrade my instance? I used the ansible playbook to install it and have no idea how to migrate to self compiled.
I feel like we’ll see 100’s of small instances falling behind because most “solo” operators aren’t going to be able to figure out the upgrade process.
I eventually did manage with trial and error but it wasn’t as simple as I thought, the documentation is a bit out of date and the nginx file for “install from scratch” is actually for docker. I still have some issues such as frequent timeouts which didnt happen before.
