platelet VS inet256

that has my package.json file and some other testing stuff. (I don't know if that's really clear, you can just look at the file structure here if it's helpful https://github.com/platelet-app/platelet)

https://platelet.app https://github.com/platelet-app/platelet

I'm working on a project to develop a dispatch system for volunteer emergency couriers, aka blood bikes. They deliver samples, blood, donated breast milk and equipment between hospitals around the UK, as well as supply blood to air ambulances.

The app is meant to replace a system of pen, paper and spreadsheets that the service is mostly being run on. I've been working directly with the charities for it to best suit their needs.

It uses React, JavaSript, Material UI, Jest, Redux and React Testing Library. Eventually I'd like to develop a React Native mobile app too.

There are some details on the issues page https://github.com/platelet-app/platelet/issues about some of the work that still needs to be done.

I have a Discord too although it's a little quiet - https://discord.gg/tWhCM98ckB

I'd be glad to hear from anyone who feels like they'd want to contribute. If you have any questions, feel free to ping me (Ducky) on Discord.

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