this post was submitted on 23 Jun 2023

131 points (100.0% liked)

Lemmy

496 readers

1 users here now

Everything about Lemmy; bugs, gripes, praises, and advocacy.

For discussion about the lemmy.ml instance, go to !meta@lemmy.ml.

founded 4 years ago

MODERATORS

nutomic@lemmy.ml

131

Lemmy v0.18.0 Release (join-lemmy.org)

submitted 1 year ago by dessalines@lemmy.ml to c/lemmy@lemmy.ml

55 comments fedilink hide all child comments

top 24 comments

sorted by: hot top controversial new old

[–] fishcharlie@eventfrontier.com 26 points 1 year ago (1 children)

@dessalines@lemmy.ml 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.

[–] dessalines@lemmy.ml 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.

[–] binwiederhier@discuss.ntfy.sh 16 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?

[–] dessalines@lemmy.ml 11 points 1 year ago

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

[–] cmeerw@programming.dev 6 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.

[–] bdonvr@thelemmy.club 10 points 1 year ago (1 children)

[–] gabriele97@lemmy.g97.top 1 points 1 year ago

I laughed a lot on it 🤣

[–] keiko@fedia.io 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

[–] poVoq@slrpnk.net 4 points 1 year ago* (last edited 1 year ago) (1 children)

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.

[–] oldfart@lemm.ee 1 points 1 year ago

It should still be possible to browse the internet with JS disabled. Especially Free Software should set a high standard to that. It's understandable that Lemmy devs have too much on their heads now, but let's not pretend that it's okay to make websites which aren't viewable without JS.

[–] eoli3n@lemmy.ml 4 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

[–] hawkwind@lemmy.management 4 points 1 year ago

Great work!

[–] Wander@yiffit.net 4 points 1 year ago (3 children)

Is it safe to update via ansible?

[–] dessalines@lemmy.ml 4 points 1 year ago (1 children)

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

[–] Wander@yiffit.net 2 points 1 year ago

Good to know. Thank you for your work!

[–] tugg@lemmyverse.org 1 points 1 year ago* (last edited 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.

EDIT: It looks like they added some extra NGINX proxy stuff in there. All that broke my instance and I had previously just deployed via ansible following the instructions on their page. I would stay away for now.

[–] Wander@yiffit.net 1 points 1 year ago

Yeah, I'll better wait for now.

[–] gnzl@nc.gnzl.cl 1 points 1 year ago* (last edited 1 year ago)

I just upgraded via Ansible and the only issue I ran into is that on 0.18.0 you can't enable Federation and Private Instance at the same time. I had both enabled on 0.17.4 and when I upgraded, the Lemmy docker wouldn't start because both options can't be enabled together anymore. I had to disable Private Instance directly on the database to get my instance up and running again.

[–] death916@lemmy.death916.xyz 3 points 1 year ago

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

[–] fox@lemmy.fakecake.org 3 points 1 year ago

very nice, updated with zero issues.

[–] Icarus@lemmy.ml 3 points 1 year ago

is the bug with "active" sorting fixed ?

[–] ledditor@leddit.minnal.icu 1 points 1 year ago

Great job... Waiting for ARM docker images to get updated

[–] briongloid@aussie.zone 1 points 1 year ago

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

[–] underscorner@feddit.it 1 points 1 year ago

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

@nutomic@lemmy.ml

load more comments