Lemmy v0.18.0 Release : lemmy

[–] [email protected] 32 points 1 year ago (1 children)

@[email protected] Thanks for the information here and all the hard work you have put into this release.

Gotta say tho, as the maintainer of Lemmy-Swift-Client, breaking API changes like this without an API version bump, make API development within the community incredibly difficult.

So my question to you would be, what is the purpose of having v3 in the API path, if the true test of API compatibility is the GetServerResponse version field? And breaking changes will occur in GetServerResponse version changes as opposed to the version in the API path? That doesn't quite make sense to me.

Would love your perspective so I can figure out how to best design the package API to accommodate client developers who might have to contend with multiple server versions.

[–] [email protected] 1 points 1 year ago

The lemmy API still hasn't hit a version 1.0, and should very much be considered beta, with a lot of active and breaking changes. When we do stabilize it, then we can start to make these breaking API changes more solid. The v3 should probably just go away at this point, because we have too much active development and API changes to justify it.

What we do on lemmy-js-client, which has its types auto-generated from rust, is use tags that match our lemmy release semver version.

I'm not sure how you built lemmy-swift-client ( I hope its auto-generated from either the rust or lemmy-js-client types), but you could do the same thing: use tags to version it, then applications could use those tagged versions.

[–] [email protected] 19 points 1 year ago* (last edited 1 year ago) (2 children)

WebSockets ... causing live updates to the site which many users dislike

I appreciate all the work in this release. It's insane how much you packed into one release. Well done. I am most excited about the live updates going away. It was quite disruptive. Thanks for that.

That said, WebSockets can be implemented very efficiently. I run an open source notification service called ntfy, and the public instance ntfy.sh currently keeps 6-8k WebSocket connections and thousands more HTTP stream (long polling HTTP) open, all on a 2 core machine with 4GB of RAM. My point being that WebSockets can be implemented very efficiently. Though in Lemmy's case it's likely not necessary.

-- Another thing I wanted to notice is that I am missing mentions of security issues in the release notes. There are some tickets that sound really really really bad, like this one: https://github.com/LemmyNet/lemmy/issues/3060

Isn't that more important than anything else?

[–] [email protected] 11 points 1 year ago

We're very busy but we'll get to it when we can.

[–] [email protected] 4 points 1 year ago

That said, WebSockets can be implemented very efficiently.

I agree, the main issue I was actually seeing with Lemmy's use of WebSockets was that when opening the main page it was continuously streaming all posts from the server (including posts in communities not subscribed to) to the browser client.

[–] [email protected] 10 points 1 year ago (1 children)

[–] [email protected] -1 points 1 year ago

I laughed a lot on it 🤣

[–] [email protected] 9 points 1 year ago* (last edited 1 year ago) (3 children)

I really appreciate the work that you're doing but...

Captchas are not available in this version, as they need to be reimplemented in a different way. They will be back in 0.18.1, so wait with upgrading if you rely on them.

What the hell? Another bad default where newbies will continue to launch instances attracting 10k+ bot signups per day and new users will keep getting disgusted by Lemmy if they land on one of those spammy instances. Making captchas a default should have been a priority and I'm sure no one would have complained if the 0.18 release was postponed to make that happen.

[–] [email protected] 16 points 1 year ago

The feed desperately needed a fix, so I'm glad they pushed it out. But agreed, they should be prioritizing methods to reduce spam and bots in the next release, even if they need to push out a relatively feature-sparse version first

[–] [email protected] 5 points 1 year ago* (last edited 1 year ago)

I was tracking the Race for Captchas in 0.18.0 and I'm pretty surprised how it went in the end.

https://lemmy.world/comment/451026

[–] [email protected] 0 points 1 year ago

I definitely would've... it was basically impossible to subscribe to communities on lemmy.world and lemmy.ml from smaller instances before 0.18.0, and after lemmy.ml updated that's no longer an issue.

[–] [email protected] 6 points 1 year ago* (last edited 1 year ago)

wow TOTP support is always welcome!!

[–] [email protected] 5 points 1 year ago

Great work!

[–] [email protected] 5 points 1 year ago

The piece of content in the feed is great and much more fun to browse ! That specific change makes me feel that I can jump from reddit to lemmy definitly.

Good work dudes <3

[–] [email protected] 5 points 1 year ago* (last edited 1 year ago) (1 children)

All Lemmy instances on v0.18.0 are inaccessible with javascript disabled. The only way to privately browse Lemmy instances now is via kbin. I was hoping that Lemmy was going to focus more on privacy with the coming updates. Maybe this will be fixed in v0.18.1?

#Lemmy

[–] [email protected] 4 points 1 year ago* (last edited 1 year ago)

JavaScript itself has nothing to do with privacy. I assume you think so because you are using Tor Browser at the higest security setting that disables JavaScript entirely?

IMHO just stop using that broken-by-design browser and use a browser extension with a JavaScript allow-list.

[–] [email protected] 4 points 1 year ago (1 children)

I thought captcha were re enabled on the rc For this but the notes say it's gone again. Adding one completely stopped botted sign ups for me

[–] [email protected] 6 points 1 year ago* (last edited 1 year ago) (1 children)

Captchas have been restored by a PR shortly before release and almost immediately been removed again by reverting the PR. The PR author has been asked to re-create his PR and then 0.18.0 got released without Captchas.

[–] [email protected] 4 points 1 year ago (1 children)

Wow that seems... Odd

[–] [email protected] -1 points 1 year ago (1 children)

The PR hadn't been reviewed and was merged by mistake, from my understanding.

[–] [email protected] 3 points 1 year ago* (last edited 1 year ago)

PR #3249 got reviewed, approved and then merged by Nutomic and then reverted by dessalines because ...

@TKilFree This got wrongly merged without a PR from me. You'll need to re-open it.

Whatever that means ...

[–] Hagarashi8 4 points 1 year ago

Man, i appreciate updates, but lemmy_api_common is now broken.

[–] [email protected] 3 points 1 year ago

That's a LOT of changes. Kudos to all the people involved.

[–] [email protected] 3 points 1 year ago (3 children)

Is it safe to update via ansible?

[–] [email protected] 4 points 1 year ago (1 children)

Yes. We have one issue open having to do with site icons, but everything else is smooth.

[–] [email protected] 2 points 1 year ago

Good to know. Thank you for your work!

[–] [email protected] 1 points 1 year ago (1 children)

I tried to upgrade via the instructions doing a git pull and then running ansible again and it totally broke my site with a server error message. I ended up reverting back to 0.17.4.

[–] [email protected] 1 points 1 year ago

Yeah, I'll better wait for now.

[–] [email protected] 1 points 1 year ago

There are multiple folks in Matrix who had issues, including myself. It only worked after using the only ansible to VERSION=0.18.0. The new ansible sets up local networks in docker-compose and such that do not work and lead to Gateway Timeouts.

[–] [email protected] 3 points 1 year ago (1 children)

is the bug with "active" sorting fixed ?

[–] qtie314 2 points 1 year ago

It seems to!

[–] [email protected] 3 points 1 year ago

very nice, updated with zero issues.

[–] [email protected] 1 points 1 year ago

are there any plan to integrate lemmybb as optional web interface ?

@[email protected]

[–] [email protected] 1 points 1 year ago

The community linking is great, is there a way to share posts natively?

[–] [email protected] 0 points 1 year ago* (last edited 1 year ago) (2 children)

I don't know how this works but I think I read somewhere that this version fixes the new post spam on browser, I checked and it's still the same, when will that be fixed? Is it an instance thing?

[–] [email protected] 3 points 1 year ago

The instance has to be running the updated version.

[–] [email protected] 3 points 1 year ago (1 children)

What does new post spam mean?

[–] [email protected] 1 points 1 year ago (1 children)

I noticed in the web client used on mobile, there would often be new posts flooding in at the top of the page. Maybe a page's worth at a time. I'm still using web client on mobile on lemmy.ml and haven't noticed this since the deployment of 0.18 yesterday.

[–] [email protected] 1 points 1 year ago

Yeah, that's been addressed.

HTTP API instead of Websocket

Until now Lemmy-UI used websocket for all API requests. This has many disadvantages, like making the code harder to maintain, and causing live updates to the site which many users dislike.