Yes, restarting Lemmy somehow resets the memory use of the database as well.

Nothing particular, but there was a strange bug in previous versions that in combination with Lemmy caused a small memory leak.

Try switching to Postresql 16.2 or later.

Hmm, there is a memory leak issue with PostgreSQL versions lower than 16.2, so instances would run out of RAM and start swapping after a while. But it would surprise me if lemmy.ml specifically was suffering from that as the devs surely know about this issue.

Yes, I also noticed that. It used to work a while ago.

If you like our communities so much, you could also create an account on slrpnk.net 😊

But yeah, two smaller instances with not much overlap in interests by their users tend to not federate well and you need to go the extra mile to search out the communities and subscribe to them.

It’s enshittified right in the design of the protocol. The entire idea of ATproto is to decentralize the annoying (& legally tricky) stuff like identity management and moderation, while keeping the profitable stuff (advertisement embedded in algorithmic feeds) more or less centralized.

And even though they are quite open about that in their technical documentation, somehow people fail to see it for what it is and think this would be somehow to their own benefit.

First of all this is mainly a feature to protect existing instances against spam from other badly managed instances.

But yes, admin approval scales surprisingly well if you have several admins per instance and many smallish instances, and it could be further improved by giving existing users secret invite links than don’t require admin approval (AFAIK also already supported by Pixelfed).

Those are largely useless against spammers, but indeed there could be other options like giving already registered users usage limited invite links etc.

Maybe the best part of the FP5 that is talked about little is that the main SoC is not a consumer grade Qualcomm chip, but an industrial grade one that will get driver and firmware upgrades for a much longer time than the consumer ones.

In addition it is fairly similar to other slightly older Qualcomm chips that already have main-line Linux kernel support, so the prospects of running Mobian or PostmarketOS on it are quite good.

Upgraded from 0.19.2 without problems. Thanks!

I don’t agree that this is something needed, but if you decide to work on it anyway, maybe try to make it compatible with Pixelfed’s Sup. https://github.com/theSupApp

Webpush or UnifiedPush would be the answers, but neither is currently supported by Lemmy.

Edit: but please don’t abuse Lemmy’s DMs as a sort of instant messenger. It’s not meant for that and also insecure. It’s meant to be asyncroneous like email at most and you don’t need push notifications for that.

The process of configurating it and converting from block storage is documented here: https://git.asonix.dog/asonix/pict-rs.git

Are you subscribed to a lot of communities and/or does it also happen when not logged in?

I suspect it might be related to loading a lot of community avatars which seem to not get properly cached in the browser or so.

I haven’t really had time to properly investigate, but I also noticed it being a bit sluggy.

Maybe you best option is to try an alternative frontend like Photon or Alexandrite.

The old OpenID didn’t see much uptake (because of the spam issue) and the alternative Oauth2 that was AFAIK mostly pushed by Google is clearly designed for the purpose of large centralized providers. So I don’t think there is a direct causality, but yes it is related.

Never the less Oauth2/OIDC works quite well and is clearly better that most of the alternatives still commonly in use.

Yes, but that is not how Oauth2/OIDC works (the old OpenID did, but it has been largely abandoned).

One of the reason this approach was abandoned is that these external login automations are very easily abused for spam if you allow arbitrary instances as the auth endpoint.

No, because Lemmy doesn’t support Oauth2 yet. And even if it would support it, at most it could be a “login with lemmy.ml” or similar instance specific button as the protocol requires a specific endpoint.

Edit: see other comment in this thread. With the OIDC discovery extension to OAuth2 it might be possible, but I haven’t seen that feature being used this way in the wild yet.

On the linked website.

Literally the first sentence:

Lemmy is a selfhosted social link aggregation and discussion platform.