Oh I was wrong, after further reading this looks to be a lot better than what I was thinking.
I must have been thinking about another methodology of attempted privacy over a dataset.
Before I start reading, if this has anything to do with differential privacy, I'm going to be disappointed.
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!
Congratulations! 👏 Happy B-day and here's to many more to my across the river friends 🎉
Ps. The video works and is great!
That awkward moment when you are the person they are talking about when running beta in production!
Bug:
subscribe & unsubscribe links are the wrong sizes on communities?listingType=Local
"Bug":
Your IP is visibleto
Suggestions:
- Padding on left side / center mode option
- Maybe its better on smaller screens, but on a 27" there is a tremendous amount of dead space.
- Comment threads are "clickable" like images?
- Instead of having to click the title, allow clicking the Comment Icon
- Instead of having to click the title, allow clicking the Comment Icon
Sent from next.reddthat.com :)
view more: next ›
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.