Foster Hangdaan

I would be careful using this service. This service stores wallet addresses as DNS records and can potentially store many of them, making it a honeypot for hackers. Anyone who can gain access to the DNS records will be able to reroute transactions by changing the addresses of the aliases.

For people who already own a domain, you don’t need this service, since you can easily setup OpenAlias yourself by adding the necessary TXT records. That is all that this service does for you.

I’d also like to add that you can save an image to a local file using docker image save and load them back using docker image load. So, along with the options mentioned above, you have plenty of options to backup images for offline use.

I recommend Peer Calls as an alternative. Peer Calls uses peer-to-peer communication similar to Jami. You can check out Peer Calls on Github for more info.

So, in short, the things I really like about it:

• Simple to selfhost - Only one Docker container with no dependencies (database, storage, etc.) and you only need to forward HTTP/S traffic.
• Lightweight - You get voice and text chat; screen and file sharing. All of it directly P2P.
• Private - Selfhosting the signaling server will grant you control over the only step which requires a central server during the WebRTC connection process.
• No accounts - Just start using, no accounts are involved.

If you need S3-compliant storage for testing and development, you can use an S3 mock server. I’ve tried the following for use in web development and CI environments, they are lightweight and configurable:

• Adobe S3Mock
• s3ninja

There is also Localstack. I found this one to be a bit more complex than the ones above and ended up not sticking with it.