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.

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!

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?

Should be fixed. (It already got merged: https://github.com/LemmyNet/lemmy/pull/4213)

If you don’t see create community in the top next to create post, then your home server doesn’t allow users to create community

No. You have to have an account on that server. (And have to use that account regularly as well, otherwise you won’t see reports about your community)

You make posts.

I use Wasabi storage which is more expensive as they have a minimum space allotment but because my servers are in Aus I had issues with backblaze b2 storage and the latency. (I was dealing with 200-300ms in network latency AU -> US + the time that backblaze takes to store the data).
At that time lemmy/pictrs was not as optimised as it is now so it’s much better now.

Backblaze comes out WAY cheaper per-month if you have servers in us/eu, as close to their regions as possible, but they also charge you for API.

As part of an Object Storage / cdn remember you also might have to pay for egress charges as well. Cloudflare is part of the “Bandwidth Alliance” but that isn’t applicable here as pictrs needs to present the images via its own domain, (such as cdn.reddthat.com). So you’ll still want a CDN infront which will mean you will only pay once for the egress instead of everytime everyone loads it.

• Minio’s free tier is a host-it-yourself. Where as their paid tier are for actual storage hosters, they have a minimum of 100TB/month @ $10/TB.
• B2 has no minimum, and egress + hosting of 20GB cost me… ($0.29)
  • Note: They still havn’t billed me because I havn’t passed the $1 mark yet!
• Wasabi (my current choice) is $7/TB (AU, US is $6/TB iirc) with a minimum of 1TB/month with out egress or api charges

Reddthat has… looks up 150GB of object storage now.

I would recommend B2 if you are starting out and are in US/EU. Wasabi in all other regions and have a CDN infront. (and don’t mind burning a little cash for peace of mind)

Don’t forget & in community names and sidebars.

Constantly getting trolled by &

To get it completely free it would need to be:

• cloudflare > vps
• cloudflare > backblaze

Because Lemmy does not have a way to have all media served from a different url/subdomain (like a CDN). Your setup will be:

• cloudflare > vps
  • vps > backblaze

Basically just put cloudflare infront of your vps, and cache everything.

That means if a user uploaded a 10MB file, it would go though your VPS, get uploaded to backblaze. When a user looks at the uploaded image url, on the first request it gets requested from blackblaze, via your vps, and then gets cached on Cloudflare.

Then any extra requests from then on will be via Cloudflare. So you will technically be charged for some api requests and 1x 10MB of egress traffic.

I would recommend Backblaze B2 storage instead of removing post history.

The problem with post removal is that it will affect all other instances’ as you don’t (by default) cache original images from other fediverse instances (iirc)

So for example, my instance Reddthat will reference an image hosted on your instance, which will then 404. (But the thumbnail will be cached (I think))

Backblaze is dirt cheap and the pictrs object migration is now multi threaded making it very easy to migrate now. I was hosting 15GB and it amounted to bills of cents! $5/TB or $0.005 per GB. If you add CloudFlare Infront you then get free egress! Or any CDN that is part of the “Bandwidth alliance”. I now have ~120GB of pictrs storage. After 2-3 months.

Also, there was a recent chat on the lemmy admin matrix channel about setting some variable in pictrs so it does not cache any images. But I don’t remember what it was so maybe check the pictrs documentation.

What a hero!