If I would need to use Eppie as a client to a third party email service to send email out to the general world, it makes adoption a very hard sell indeed.
Google defederated their XMPP infrastructure. Do you think they wouldn't do the same with GMail, if they could afford to?
Do I have to run my own node - on a server in my basement, or on a VPS?
Do I have to trust your infrastructure?
Do I have to go through another, existing provider?
I'm trying to get a simple answer to these questions since my original post.
To create a gateway on your domain, you should run your own Eppie node and set MX record to point to that node. Otherwise, there’s no MX record. It’s a p2p trustless network
> Do I have to run my own node - on a server in my basement, or on a VPS?
Yes, as soon as Eppie is launched.
> Do I have to trust your infrastructure?
Eppie is a trustless network. All nodes are equal. So, no, you don’t have to trust it. Take a look at our GitHub: https://github.com/Eppie-io
> Do I have to go through another, existing provider?
No you don’t.
> I'm trying to get a simple answer to these questions since my original post.
We appreciate your willingness to get to the bottom of it.
- One-way gateway from the conventional email to our decentralized network. So you can still receive emails from conventional email to your decentralized address.
- Eppie can work as a client to conventional email when you need it.
- Eppie can use conventional email addresses for decentralized message delivery, so no data lands on any server (both participants must be Eppie users)