this post was submitted on 23 Jun 2023

50 points (100.0% liked)

Pawb.Social Announcements

403 readers

1 users here now

Official announcements from the admin team of Pawb.Social

founded 1 year ago

MODERATORS

[email protected]

Pawb.Social updated to Lemmy v0.18.0 (pawb.social)

submitted 1 year ago by [email protected] to c/[email protected]

22 comments fedilink hide all child comments

We've just updated to the latest version of Lemmy which comes with a ton of bug fixes and an updated UI without websockets (yay, easier debugging).

You can find the full changes over at https://github.com/LemmyNet/lemmy/releases/tag/0.18.0.

This also appears to have fixed an issue with connecting to kbin instances. You should now be able to search those up in the same way as other Lemmy communities: !community@domain, but let us know if there's any issues!

top 17 comments

sorted by: hot top controversial new old

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

Also, apparently there's emoji now... Just the implementation is a bit... jank XD

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

🏳️‍🌈

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

Lol, see I thought the move away from Websockets was a bad call on their part, namely because of the reasons they gave for doing so. But, if it makes debugging easier, then that works too. xD

Be curious how the load on the server changes moving back to HTTP instead.

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

Websockets cause continuous strain on servers regardless of if the user is even interacting with the site

With HTTP/2 or even 3, it should be much less load overall. Especially if they optimize their API a bit better.

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

Was the server downgraded after maintenance today? Jerboa is now throwing up a message we're under the minimum supported version (0.18).

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

Stand by, I just realized the version isn't even showing up in the UI...

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

Apologies for the delay, GitHub went down yesterday so I couldn't pull the build tag. Should be fixed now :3

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

This UI already feels way better for reasons I can't even quite describe. Nice!

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

The darkly theme looks a tiny bit broken in some places. darkly-red looks more polished for some reason.

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

Mind taking some screenshots of the problematic areas?

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

Open these both up in new tabs and flip between them

darkly:

darkly-red:

Also on the darkly-red theme there's still some aqua/blue colors laying around, but I'm not sure if that's new:

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

darkly seems to be fixed now

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

Searches occasionally render the error "couldnt_find_object" here for me. I can't quite tell if this only started happening after the update or not since I'm quite new here.

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

It does seem like it is a new issue since 0.18.0.

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

How was the upgrade? Simply running ansible?

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

Yep! But I had a scare for a little while as it initially migrated and loaded everything. There seems to be a lot less output in the docker logs command too which is unhelpful and nerve wracking.

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

Thank you! I'll probably give it a try tomorrow!

load more comments