70
Why do so many services require email configuration?
(piefed.social)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 12 Nov 2025
70 points (90.7% liked)
Selfhosted
62951 readers
679 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 3 years ago
MODERATORS
You don't have to write code to configure Matrix/XMPP.
You keep saying this as if user adoption is the only thing that matters. 99% of self-hosted stuff has tiny "userspace" so I don't know what you're on about.
You do realize that the developers need to write code to configure a Matrix/XMPP module? The module doesn't just appear out your immagination.
Then it will need to be maintained as security holes are discovered.
Tell me again why developers should spend the time and resources to maintain a feature that at best will have a marginal impact on the userbase, over focusing on the core of the project.
How you imagine things send messages to reset your passwords, sending notifications and whatever is currently managed via email than some piece of code creating and sending messages, managing possible errors with them and potentially also monitoring/logging the message traffic for statistics or debugging?
User adoption matters if you want your thing to be actually useful for the actual users. And supporting any messaging system requires effort, so it makes sense to spend limited resources on a thing which has the biggest userspace. If you want to run matrix server which has you and your dog using it, go ahead, but don't be surprised if you want to contact your neighbor and he'll look like you have two heads when you start to explain how to reach you.
It makes zero sense to spend any resources on adding compatibility with proprietary and malicious protocols, regardless of "userspace".
I had a look at the system, and it is a commercial product, I would imagine that their customers have requested these features.
Since you are a customer, why not request your features to be added as well?
Or, better yet, since you have explained that creating an XMPP/Matrix module as an alternative to email requires no coding, and the plattform is open source, why not just slap it together yourself?