Right, but that could have been delayed until prod release. It would give the developers of 3rd party apps chance to adopt rather than scramble and push last minute fixes.
Plus I'd imagine that a lot of users that aren't super technically inclined might open their apps, try to use them, fail ungracefully and give up on the idea of lemmy.
Thank you for upgrading! I know these things aren't easy. Especially for a new(er) platform like Lemmy
Some more notes on what is included in the 0.19 version. Personally, for this instance the 'rewrite images to use local proxy' feature for privacy and the scaled sort option for vitalizing smaller communities look especially promising
no offense to dev but he seems like he abandonned the app. although i can't blame him really: there is no financial incentive to keep supporting it. Hope the web version catches up to all those cool app features
This update also disables 2FA for all accounts. 2FA also now uses SHA-1 instead of SHA-256, so it follows now RFC 6238. Should make the Lemmy 2FA method compatible to more TOTP clients.
Tying into a discussion on Boost for Lemmy. 0.19 is in beta, why did the instance decide to go to a beta release? Not attacking anything just trying to understand.
In sum; I needed some features of this version in backend. We were in 0.18.3 which is so old. Couldn’t waited. This is an exception BTW. Will not happen in the future.
So, it has only been two days worth of posting for me, but the upload process is MUCH better. Images which normally would have taken two or more attempts, now upload the first time.
As of 6:50 PM GMT, when I upload an image, it does not show on the upload page, and directly linking to the URL provided for the uploaded image returns {"error":"auth_cookie_insecure"}. Tried in two different communities. Will check back in a few hours, and try my posts again.
6:04 PM GMT. Using the web-ui client. Upload with chrome gives the same problem. Upload with firefox works, and post is visible to both chrome and firefox. Uploaded second post with firefox, and uploaded ok, but does not show in the community with either firefox or chrome. Reloaded in both browsers 6+ times. Post does show when go to the front page feed, and sort on new. Post in question is https://lemmynsfw.com/post/5009195
On the first render of the web UI I get shown posts from blocked communities. (opening lemmynsfw.com in a new tab) If I refresh the page they're gone. Anyone else has this problem?
It appears you have updated to 0.19.2. The Modlog no longer shows what the action taken was. For the little bit that of moderating that I do this is not a problem, but may be for more active mods. This is mostly a just FYI post.
Screenshot of what I see. I am running Chrome 120.0.6099.216 on MacOS. Checked in Firefox (121.0.1) and I see the same thing. The first five lines were approved after review (was a bug in the client that @NotAtAllSafeForWork was using. The next one was un featuring the post. Last one you can see clearly was deleting a comment, I believe. As you say, Interesting.