@tomw Apologies; I wasn't trying to suggest you shouldn't do this. I was only trying to emphasize that there is an entire system/chain that leads to your server.
You might have:
The nation-state working in tandem with local (or, are they state-owned?) ISPs to implement man-in-the-middle cert attacks, so that attempts to securely connect to your server are actually plain-text.
The nation state, working with ISPs to compromise/log all traffic through DNS servers.
...
https://www.cisa.gov/news-events/alerts/2015/04/30/securing-end-end-communications
is an article that speaks to some of the kinds of things that you might have to do to begin securing end-to-end communications.
Ultimately, I really don't know. I'm just suggesting---YMMV, etc.---that this sounds like something with high stakes.
I wish you and your colleagues all the best of luck.
PS. https://www.cjr.org/tow_center_reports/guide_to_securedrop.php looks interesting as well. Again, it doesn't apply directly to your case, but speaks to the broad spectrum of design considerations that go into architecting and delivering secure systems, where "systems" means "a combination of technology and people."
