

Because once it leaves the server there is no guarantee that the remote server understands or even respects the notion that it should be private.
Lemmy doesn’t have private communities yet afaik.
Admin on the slrpnk.net Lemmy instance.
He/Him or what ever you feel like.
XMPP: povoq@slrpnk.net
Lemmy alt: @kris@feddit.org
Avatar is an image of a baby octopus.


Because once it leaves the server there is no guarantee that the remote server understands or even respects the notion that it should be private.
Lemmy doesn’t have private communities yet afaik.
OIDC isn’t “innately centralized”, thats just how the majority of people use it. And the same will be likely true for FedCM.
Extremely annoyed at users that think everyone has iOS phones, when most of the world have Android. Thinking that the US is the only relevant place means you have serious tunnel vision. /s
Oh and blame Apple. They are extremely hostile to open-source devs publishing apps on their platform.
Sounds good, but this FedCM seems to be basically a reinvention of Oauth2/OIDC. Even if it brings some minor improvements (credentials storage in the browser or so?), it seems dead on arrival given that there doesn’t seem to be a strong dissatisfaction with how OIDC works. Or am I missing something?
Probably a bad idea to congest the limited bandwidth of Tor with voice chat.


It was actually the British: https://en.wikipedia.org/wiki/Operation_Big_Bang


But you do realize that DeltaChat also received a quite significant amount of money from the US Open Technology Fund over its course of development and to this day it is somewhat unclear how they fund what seems to be several full time developers?
The app itself might be fine, but you are either using the Mozilla services or the backend written by Mozilla. Sadly Mozilla has lost all the good will it had and is just another silicon valley AI company these days, and seems to prefer it that way.


That article has a strong AI slop smell.
That’s from Mozilla, another AI company…
The first three on this list can do it: https://joinjabber.org/docs/apps/android/
Explanation here: https://joinjabber.org/tutorials/service/unifiedpush/
If you use ntfy mainly as a Unified Push distributor on Android, then I highly recommend switching to a XMPP client that can do the same.
https://github.com/lldap/lldap is much simpler.


Good question, but I think you will need to ask the original author.


I recommend Forgejo over Gitea, and you definitely need an AI scraper blocker like Anubis in front of it as otherwise they will kill your VPS rather quickly, as these AI scrapers absolutely love to scrape code forges.
UT reuses the Android Linux kernel and drivers, so that can’t be compared 1:1 to (near) mainline Linux kernel using distributions.


Movim has good support for https://slidge.im/ based gateways that include WhatsApp and Telegram.


This seems like something that would really benefit from better language support. I saw the translations folder in the repo, but you should probably get it linked up to a Weblate instance or similar and have people start contribute different languages asap.


This is indeed excellent and they are currently working hard on making it a nice alternative to Discord.
Our Lemmy instance has been running it as a supplementary service for quite some time now and it is relatively popular with our members: https://movim.slrpnk.net/
You might be confusing the old OpenID with OIDC (short for Open ID Connect), which is based on Oauth2, an entirely different technology.
OpenID was definitely more decentralized compared to how OIDC is commonly used these days, but OIDC has various little know options to do similar things.