This is sso support as the client. So you could use any backend that supports the oauth backend (I assume, didn’t look at it yet).

So you could use a forgejo instance, immediately making your git hosting instance a social platform, if you wanted.
Or use something as self hostable like hydra.

Or you can use the social platforms that already exist such as Google or Microsoft. Allowing faster onboarding to joining the fediverse. While allowing the issues that come with user creation to be passed onto a bigger player who already does verification. All of these features are up for your instance to decide on.
The best part, if you don’t agree with what your instance decides on, you can migrate to one that has a policy that coincides with your values.

Hope that gives you an idea behind why this feature is warranted.

https://reddthat.com/signup

2nd best reporting in.

A faster db. Just the regular performance benefits, https://www.postgresql.org/about/news/postgresql-16-released-2715/

Also, Lemmy is built against v16 (now) so at some point it will eventually no longer JustWork

The script will be useless to you, besides for referencing what to do.

Export, remove pg15, install pg16, import. I think you can streamline with both installed at once as they correctly version. You could also use the in place upgrade. Aptly named: pg_upgradeclusters

But updating to 0.19.4, you do not need to go to pg16… but… you should, because of the benefits!

That awkward moment when you are the person they are talking about when running beta in production!

Since the 11th @ 9am UTC, LW has seen a 2 fold increase of activities. If my insider knowledge is right (and math) it’s 7req/s average up from 3req/s.

Lucky for both of us we are not subbed to every community on LW but I think we are subbed just enough to be affected.

Relevant: https://reddthat.com/comment/8316861 tl;dr. The current centralisation results in a lemmy-verse theoretical maximum for of 1 activity per 0.6 seconds. or 100 activities per minute. As total transfer of packets is just under 0.6 seconds between EU -> AU and back.

Should be already fixed. I’ve logged out and in on Jerboa.

We rebuilt the Lemmy container with an extra logging patch. Seems build docs need some work? as that’s the only difference in the past 1-2 days, except for moving to postgres 16…

Thanks for the ping.

I’ve gone back to mainline Lemmy. @Morpheous@lemmy.today check now please

See my PR for a new backup script. https://github.com/LemmyNet/lemmy-ansible/pull/210

I’ll get to adding it to the main docs on the weekend.

Tldr, piping your backups via docker is CPU expensive. Directly writing to filesystem in a postgres compatible format with compression is faster and more efficient on the CPU.

My 90GB+ (on filesystem) db compresses to 6GB and takes less than 15 mins.

Been running this since -rc1 & 0.19.1 for the past 13 hours. No issues related to Federation since! just higher CPU load compared to 0.18.x releases.

Thanks for another great release. Suppose I should go fix our ansible ey?

No worries! I hope the community comes back around!

Yeah funding is good. Completely community funded :) Ours is on open collective if you want to see it 😉 (we are completely transparent)

We (reddthat) would welcome your community. 😉

What a hero!