Comment on Why do so many services require email configuration?
frongt@lemmy.zip 2 weeks agoThen you’re free to patch it out.
Comment on Why do so many services require email configuration?
frongt@lemmy.zip 2 weeks agoThen you’re free to patch it out.
artyom@piefed.social 2 weeks ago
Why do you assume everyone you interact with is a software developer?
MonsterTrick@piefed.world 2 weeks ago
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
artyom@piefed.social 2 weeks ago
I wasn’t asking for advice, I was asking for an explanation.
frongt@lemmy.zip 2 weeks ago
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.
porcoesphino@mander.xyz 2 weeks ago
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
artyom@piefed.social 2 weeks ago
I wasn’t asking for “options”, I was asking for an explanation.
porcoesphino@mander.xyz 2 weeks ago
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?