alyx

This could be done via some sort of a "soft delete" mechanism (It's worth noting, this is entirely theory-crafting based on how I've implemented similar systems elsewhere): - Intensely destructive...

@ilbelkyr do you have thoughts?

Ah, I saw that but assumed that was only the situation when running behind a reverse proxy. Perhaps it would make sense to copy that warning over to https://docs.meli.sh/configuration/ssl ?

I don't know that there's a ton of value in having clients relay that information since, frankly, it seems like a poor idea to trust what another client says in...

My immediate thought here is to include a contrib.conf.example which gets installed to $ATHEMEDIR/etc next to atheme.conf.example when `--enable-contrib` is enabled. This would keep atheme.conf clean from the misc. contrib...

That's what I was thinking; have a commented include in atheme.conf or something along those lines. @aaronmdjones brought up a good point on IRC as to how flexible Atheme's config...