ubikom VS inet256

Excellent client, btw. I have an issue open regarding this, but when I tried it seems to work fine. The client autoconfigured itself. If you are having issues with em client, please PM me or comment on the issue here: https://github.com/regnull/ubikom/issues/58

Thanks for reporting the issue. You can track it here: https://github.com/regnull/ubikom/issues/54

I'm working on https://ubikom.cc, end-to-end encrypted email service based on the concept of self-sovereign identity. Basically, you keep the encryption key, and all your messages are encrypted, on the wire or at rest. The core platform is open-source, the code is available here: https://github.com/regnull/ubikom

Billions of users use GMail (or similar services). These companies are making money by selling ads, and their "free" email service is just another way to improve ad targeting. Furthermore, your account can be disabled at any time and for any reason. Sure, you can switch to Protonmail, Tutanota, etc. because they are "good" companies. But why do you have to trust to any of them? Keep your encryption key, and have communication providers move around encrypted bytes on your behalf. Store your identity on a blockchain (maybe), so that no one can take it away.

That's the idea. If you'd like to work on something like this, get in touch. lgx (at) ubikom.cc

Shameless plug time! I'm working on 100% encrypted/authenticated email based on Self-Sovereign Identity and decentralized key registry, check it out at https://github.com/regnull/ubikom

My approach to hosting with Got has been to make it easy and secure for users to host from any machine.

INET256 solves that problem nicely. If you have access to an INET256 network, then all you have to do is swap addresses and two Got instances can communicate.

https://github.com/inet256/inet256

Also, end-to-end encryption is table stakes. Any data that leaves the user needs to be encrypted in transit, and if it hangs around away from the user, at rest.

I'm working on INET256, an API for secure identity based networking. The reference implementation, mesh256 is a mesh network using a distributed routing algorithm. There is also diet256, which is a centrally coordinated network with direct connections using QUIC over The Internet.

https://github.com/inet256/inet256

https://github.com/inet256/diet256

Thanks for sharing RocketGit. This is the first time I've heard of it, and yes, it does look like a cool copyleft solution to self-hosted Git.

Another interesting option is Brendan Caroll's got[0], which allows sharing of repositories over INET256[1]. I'm sure there are other P2P approaches to Git, but this one just piqued my interest. Unfortunately it has a naming conflict with OpenBSD's Game of Trees[2].

[0] https://github.com/gotvc/got

[1] https://github.com/inet256/inet256

[2] https://gameoftrees.org/

I'm working on INET256, a 256 bit network address space for easily and securely connecting applications.

https://github.com/inet256/inet256

- The API is focused around sending and receiving messages to addresses derived from public keys.

- Each application can have its own stable address.

- Runs as a daemon process which is configured with peering information. Additional network nodes can be spawned through the API.

- Can easily support arbitrary routing algorithms through a well defined interface.

- A TUN device (similar to CJDNS or Yggdrasil) is included as a separate application. (The IP6 Portal)

https://github.com/inet256/inet256

Developers, applications, and end-users are under-served by the network layer. INET256 provides necessary features (stable addresses, encryption) to client applications, which usually have to reimplement those features themselves.

There is an interface for address discovery [1] (finding transport addresses for peers you know about) and autopeering [2] (peering with peers you didn't know about beforehand). There is an unfinished branch for LAN broadcast discovery/autopeering. Contributions are definitely welcome here.

I had played around with a STUN transport, but the easiest way to connect has been to stand up a cloud VM with a static IP.

INET256 addresses use the same public key serialization as TLS, but they intentionally avoid the rest of the certificate infrastructure complexity. They make great leaves in a web of trust. You can sign them, or stick them in DNS records. And if you don't want to deal with any of that, fine, just swap addresses and you can communicate securely.

[1] https://github.com/inet256/inet256/blob/master/pkg/discovery...

> To me, this is the future. I wish we had a set of APIs to allow connecting to a public key instead of an IP address

INET256 is working on exactly that. It's a set of APIs for connecting to addresses derived from public keys.

https://github.com/inet256/inet256