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
62922 readers
1160 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
I don't want email to be accessible to those services. I don't want those services to use email at all.
Then you're free to patch it out.
Why do you assume everyone you interact with is a software developer?
To be fair, you are on a Self-hosting community but maybe read up the wiki or file the issue to suggest an option to make it not required on their git repo? 🤷
Otherwise, I'm not sure what else are we suppose to say
I wasn't asking for advice, I was asking for an explanation.
You should probably ask the developers then. But the answer is probably to support things like password resets in environments with multiple users. It's less development effort to implement it this way than to maintain multiple code paths with varying levels of account management.
...which ones?
https://github.com/TryGhost/Ghost
This is the repo (unless I have the wrong software).
However, it seems they’re running a business, which means revenue generating features will probably be prioritized. They’re not running a charity.
I’m sure if you donate enough money you can probably get them to implement better self hosting functionality. Chances are the email requirement is just what they have for other features.
Ghost is just one piece of selfhosted software. But I have inquired and they have declined.
They are, actually. They're a registered non-profit.
More unnecessary functionality.
What was their reason for declining?
I see they’re a non profit business. That doesn’t make them a charity. They have paying customers.
I don't think that assumption was inherent in the comment
If you want an unpopular feature that doesn't exist on an open source platform sometimes your only options are to code it, or ask someone else to. The skillset of the feature requester doesn't change that
I wasn't asking for options, I was asking for an explanation.
In your OP, sure.
But this comment reads as a desired state, and in some situations thats a feature request (in this case it seems like there are architecture / system workarounds):
Did you get an explanation you're happy with?