You can ask questions about the Lemmy.nz instance here.
This community also serves as our Meta community, with posts about updates to the Lemmy software on Lemmy.nz or other things relevant to Lemmy.nz users and not relevant to other instances.
Apologies for the bit of downtime. I've just updated Lemmy.nz to 0.19.10 as well as aligning our nginx config with the latest config from the Lemmy repository. We had been running an original one from when the instance started, with some custom changes. Now we should benefit from changes over the last couple of years.
DMs are now removed when banning user with content removal (i.e. deletes scammer "Nicole the Fediverse chick" DMs)
Resolving some language setting issues
I was hoping to solve a video streaming issue but the update to the nginx config doesn't seem to have helped so I need to play with it some more. So there may be more brief outages tonight but I will try things in my test instance first.
It would be nice if everyone would use tags or brief quotations, so I can see who is replying to who.
Modern forums are confusing my old brain because I'm used to the old BB code and old style of forum navigation, but a lot of things have changed in Lemmy, and also with proprietary forums used by large companies.
Sometimes I forget how to use features. I'm no better than a boomer who needs constant reminders on how to hold a mouse.
I think some people either don't care or they simply forget that you can highlight text with the mouse and then click "reply" to make a quotation. Maybe they are using a phone and it's too difficult to do this.
We had about 10 mins of downtime starting from 1:17 this afternoon as the database migrations ran. Apollogies if this interrupted your lunchtime scrolling, this was needed because the Controversial scores needed to be re-calculated as detailed below.
We have skipped a few versions, we were on 0.19.5, and so we have .6, .7, and .8 updates. A brief summary follows, with links to the Lemmy announcements.
This version introduces parallel sending, which should solve our issues with Lemmy.world and remove the need for the extra VPS in Finland. Unfortunately Lemmy.world needs to update for this to work, so it will be a while longer.
Changed sameSite cookie from Strict to Lax - I think this should help the issue where you are logged out from the browser a lot (especially in Firefox)
There's a change in how "Controversial" is calculated, to use exponents instead of m
TL;DR: Lemmy upgrade some time early in the new year. I also recently enabled image proxying, let me know if you noticed.
I thought I'd make a quick post just to explain the plan for updating Lemmy.nz to the latest Lemmy version and another recent change to image proxying.
Lemmy upgrade
Some of you make have noticed that Lemmy 0.19.8 just came out, and yet we are still on Lemmy 0.19.5.
There have been various bugs in 0.19.6 and 0.19.7 that while not critical, there was also no reason to rush the upgrade and I decided to wait for 0.19.8 which had a fix for some thumbnails not working that was broken in I think 0.19.6.
My plan is to give a little time to see if others have issues, and then upgrade to 0.19.8. Most likely this will be early in the new year. I don't believe there should be any significant downtime so I will probably just do it when I am ready. Before I do, I'll do a test run and see how long it takes,
Xi wants to experiment with using xi/drag person-independent pronouns on this account. So far xi likes using the pronouns, but xi's only written 4 comments and already someone accused drag of talking about Chinese politics when xi mentioned dragself. Xi knows xi's pronouns are confusing, so xi would like to put xi's pronouns in xi's displayname to clear things up.
But the character limit for display names on lemmy.nz is only 22 characters, and xi's handle already takes up 16 characters. Xi would need 24 characters to put xi's pronouns in xi's display name. Xi knows some instances also have a separate field for pronouns, and the pronouns get displayed next to the name without taking up displayname characters. Xi would like a place, or at least enough room, for xi's pronouns, please.
I use bromine as my browser on Android and when I navigate to the lemmy.nz homepage in bromite the "All" button does not work. Works fine on lemmy.world, issue with latest update?
Version 0.19.5 is a minor release with some bug fixes for 0.19.4. We were never running 0.19.4 so the bug fixes are less important than that new features in 0.19.4.
The upgrade took a bit longer than expected, perhaps 40 minutes of downtime. Partly this is because of an issue with postgres memory that happened before I started the actual upgrade.
Probably the two biggest new features for users are the ability to hide posts, and the ability to see any images you've uploaded (since lemmy started tracking).
There is also a new setting to change how upvotes are displayed, and we have a new option to have communities that don't federate. Maybe this community is a good target for that? L
Lemmy 0.19.5 has been released with some bug fixes, and we haven't upgraded to 0.19.4 yet, so I'm planning on doing the upgrade (to 0.19.5) this weekend.
Sorry, site seems to have been down from about 8pm last night through to about 7:30 this morning.
I spotted it last night and thought it was back up, but it seems some component wasn't so it was loading the pages but you couldn't do any actions.
It also means federation is behind because instances wouldn't have been able to contact us, and so that will be slowly catching back up. It may take a while because after a lot of downtime the instances will stop trying for a while.
TL;DR Lemmy.world posts, comments, votes coming to lemmy.nz have been delayed by a gradually increasing amount over recent months, peaking at about 4 days behind, but we should be back on track soon.
Background
Check the above post for some background, but TL;DR our server is in Auckland, NZ and Lemmy.world's server is in Helsinki, Finland. We are about as far apart as we can get from each other. Because Lemmy can currently only send one action at a time (Post, comment, vote), we can only accept about 4 or 5 actions per second as it takes around 1/5 of a second to make the round trip. Lemmy.world is now creating more than this on average, which means we have been falling behind more and more.
Pre-fetcher
After that post, things continued to get worse. While hanging out on Lemmy Matrix
TL;DR possible thumbnail and local image outage tonight
Tonight I plan to update the image engine behind lemmy, called pictrs, to the latest stable version and to also perform a migration to a different database (sled to postgres).
In my testing there was minimal outage, but it did take quite some hours to do the migration (12+, though my test server is a lot slower than the production one).
Once the migration is complete, I intend to turn on a thumbnail cache cleaner that will significantly reduce the size of the thumbnail cache on the server. Lemmy currently saves many thumbnails locally, and never deletes them. This means we have over 260GB of images that get backed up each night for no reason. Lemmy makes it hard to tell the difference between cached images and user uploaded ones, but the cleaning tool will go through each post in the database, find the thumbnail associated with it, and delete it if it's more than a month old.
I though I'd better make a post about recent lemmy.world federation issues, since not everyone sees the daily posts.
TL;DR:
Lemmy.world inbound federation is about 18 hours behind, and slowly catching up.
Outbound is fine: If you post or comment on something in a lemmy.world community, it will be almost instantly federated to other users, but if they reply to you then it will take 18 hours before you see it.
It was caused by an assumed Kbin bug in combination with a lemmy bug
All other instances seem fine for inbound and outbound federation
On Thursday last week Lemmy.world began to receive hundreds of thousands of "activities" (actions - comment, post, upvote, etc) from Kbin to their communities. These actions then federate from Lemmy.world out to any instance with users subscribed to those communities.
Unfortunately, this also helped uncover a big issue with how Lemmy handles inbound federation. Actions are sent one at a time, and the next can't be sent until the last is