slashzero

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

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

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

Yay! Thank you for confirming

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

Yay! Small victories

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

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.

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

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

Active daily user count is about 50k.

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

Great write up!

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

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

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

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!

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

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…

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

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? 🤷‍♂️

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

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)

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.

view more: ‹ prev next ›