I bet they will move all the space-X live streams off of YouTube and onto Twitter X and require a paid subscription.

Yes, there is: 0.18.2-rc.1, which has the hot fix, but will also require a DB query to "fix" the modlog once upgraded.

Same!

Also the source of a great meme!

There are so many great episodes to chose from. Since most of the ones I’d pick have already been listed by others, here are my favorites that haven’t been mentioned yet:

• Time’s Arrow
• Cause and Effect
• Relics
• Data’s Day

Time’s Arrow is such a great two-parter, I’m surprised no one has mentioned it yet!

For me it’s 3AM rewatching a Star Trek series I’ve already watched many times (in this case, Voyager), knowing full well my work day starts in 5 hours.

Is there anything Grafana cant do?

I have so many things pumping data “into” Grafana these days I’m surprised they haven’t tried to force me to pay for an enterprise license.

Anyway, thanks for sharing these, @ruud@lemmy.world. As a performance engineer, I love to see this level of detail and commitment on your part to keep the user experience for lemmy.world at acceptable levels.

Easy one to miss! The documentation isn’t very detailed. 🙂

What is your domain set to?

Also I think the !selfhosted@lemmy.world community might be a better place to ask for help.

I recommend using the docker images directly. As you see, the ansible scripts are basically another abstraction layer used to build the docker containers and their configs (and has string substitutions like {{some_string}} which are not valid for docker-compose.yml). Some will disagree but I feel ansible adds unnecessary complexity to deploying lemmy containers.

Anyway, glad you figured it all out!

That’s most definitely a bug, in my opinion. Might want to file an issue on GitHub.

Hi there! This sounds like you might just have a typo in your docker-compose.yml file. It might be helpful if you posted your docker-compose.yml contents here (be sure to remove any sensitive information).

Line 26 of my docker-compose.yml file is the volume block/map for letsencrypt. Did you perhaps mix tabs and spaces, or have one too many spaces in your indentations, in your yaml file? That's a no-no...

Personally, I setup my instance using the same guide as you, opting for the docker containers. There were definitely a few pitfalls to deal with.

As a Performance Engineer myself, these are the kind of performance improvements I like to see. Those graphs looks wonderful. Nice job to all.

Neat! I’ll definitely check this out.

Hi there!

TL;DR: probably have an nginx misconfiguration. Check the nginx logs for errors.

You don’t need to install and run nginx on the host. It has its own container in the docker-compose.yml which gets started up on docker-compose up -d

If both instances of nginx are trying to bind to the same port, one will start and one will fail.

Is the lemmy proxy nginx docker container running? Check with: docker ps or docker container ls. If the lemmy nginx proxy container isn’t running, try stopping the host instance of nginx (systemctl nginx stop) and restart docker lemmy (docker-compose down, docker-compose up -d), then try to access your site again.

I also work from home. WFH for life! Never going back.

Hell, I went for the longest time resisting the urge to get one, as I have a great gaming laptop (RTX 3070ti,) and eventually caved in. The draw of being able to play anywhere, anytime, plus the hype, is what eventually convinced me. The Steam Deck is pretty amazing, and worth every penny.

I hope it is released soon as well. I'm hoping some of the other open issues are addressed.

Currently there are 15 lemmy-ui bugs open, and 20 lemmy backend bugs open, against 0.18.0.

• lemmy backend bugs
• lemmy-ui bugs

Upgrading my instance to 0.18.0 has caused a lot of problems. One major issue is the main web UI won't even load (returns a blank page with just text Server error), unless you manually remove the site's image icon via a SQL query in the Postgres database. So, upgrade to 0.18.0 at your own risk.

Also, this is not intended as a criticism to anyone. Just a warning that 0.18.0 is a bit unstable and waiting for 0.18.1+ is a safer option for the larger hosted communities (my opinion).

I think the safest option is to not host from your home network. If you aren’t up to date on security patches, you could potentially expose a lot of data from an insecure server running inside your network.

There are precautions you can take, like isolating any external facing servers from the rest of your network, for example, but I generally recommend using a hosted service instead.

From a real-world perspective, I suspect that the headskirts were originally created to avoid creating a full head prosthetic for guest actors. Once the character of Quark was created, the cost of a reusable full head prosthetic would have been less prohibitive.

Your suspicion is correct. Several behind the scenes videos and past producers have confirmed this as the main reason. Not only cost, but time needed to do the full head makeup.

Don’t upgrade to 0.18.0, @ruud@lemmy.world!

Oh, good idea! Whatever works for you. I spent several hours yesterday trying all sorts of networking hacks to resolve the issue on my instance. I eventually found a combination that worked for me.

The concern here is we are all solving this issue in slightly different ways on our self hosted instances. Eventually, I hope the lemmy dev team releases 0.18.1 fixing all these issues for good.

One other thing I did was update my resolve.conf so that valid DNS IPs were making it to the containers. Otherwise the containers might not have valid DNS. Also try rebooting your host.

Here is what I did to fix the container DNS lookups failing:

https://stackoverflow.com/questions/20430371/my-docker-container-has-no-internet

Oh, this span builder error. Yeah I’ve been seeing that error since I upgraded to 0.18.0. Sorry, I don’t have a solution for this one.

Glad you figured out your pictrs error though! One other thing I did was update my resolve.conf so that valid DNS hosts were making it to the containers. Also try rebooting your host.

Feel free to add to this discussion. https://github.com/LemmyNet/lemmy/issues/3314

Yay! Thank you for confirming

Yay! Small victories

I turned that off, as well as show online status, years ago.

You should disable tracking everywhere you can. Opt-out of personalized ads. Enable the do not track feature.

There was a pretty big jump in active instances, too!

Active daily user count is about 50k.

Great write up!

What is wrong with using communities? By the way, in kbin they are called magazines.

Are you running lemmy 0.18.0? It breaks a bunch of internal network connectivity. The short term solution is to add an external network to both the lemmy-ui and pictrs containers, then you can change http://pictrs:8080 to http://your_domain.

Note: there are also some issues in 0.18.0 with comment federation at the moment. Please reply to confirm this comment was seen, thanks!

Huzzah!

Commenting to bookmark this for future reference! Great write up. I’ll likely try this on my instance at some point.

Also testing to see if my comment shows up…

I ended up nuking my Postgres DB, and recreating that container from scratch. Not sure what went wrong, but it feels like some data in the DB when upgrading from 0.17.4 to 0.18.0 perhaps broke stuff? 🤷‍♂️

I was just looking at the changes and there is a commit to add 2FA support.

Here are the diffs (0.18.0 vs 0.17.4)

• lemmy-ui
• lemmy backend

Look at the footer on your home instance to see if they are running 0.18.0 or 0.17.4. If 18, you should see 2FA settings somewhere.

Here are the changes related to 2FA.

You can load the project directly in GitHub and do a diff between 0.17.4 and 0.18.x.

Here are the diffs (0.18.0 vs 0.17.4)

• lemmy-ui
• lemmy backend

Awesome! Thank you for posting this. I will be updating my instance as soon as I can.

It’s the gold rush of lemmy/kbin apps!

Is… is that a photoshopped nail?

The question is: what percentage of those users are bots? And does it matter?