This is a quick proof of concept still in the works.
The way this works is you set up a longterm device at home, this is always on. Its like a physical mailbox.
The server manager sets up two onion services/dependencies. One to be used as the web ui in which you access your mailbox. By default, this is an authenticated service. The authentication key is generated at first start up.
The second address is your receiver service. This is where you are reached. The format is [custom]@[123xyz...onion]
When you send a message through the webui, it gets qued for sending on the always on home server, then sent to the receiving side inbox through api endpoint.
smalltorch•56m ago
The way this works is you set up a longterm device at home, this is always on. Its like a physical mailbox.
The server manager sets up two onion services/dependencies. One to be used as the web ui in which you access your mailbox. By default, this is an authenticated service. The authentication key is generated at first start up.
The second address is your receiver service. This is where you are reached. The format is [custom]@[123xyz...onion]
When you send a message through the webui, it gets qued for sending on the always on home server, then sent to the receiving side inbox through api endpoint.