rs-soroban-env
inet256
rs-soroban-env | inet256 | |
---|---|---|
1 | 14 | |
57 | 133 | |
- | 0.0% | |
9.4 | 4.6 | |
3 days ago | 10 months ago | |
Rust | Go | |
Apache License 2.0 | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rs-soroban-env
-
Ask HN: What Are You Working on This Year?
Continuing to work on the soroban-sdk[1] and soroban wasm environment[2], but after spending last year completely immersed in Rust, which was exhilarating learning experience, I'm really hoping to find some ways to spend more time back developing in Go soon and hope to do more of that this year, but unclear on exact plan for that yet.
Also hoping to find some small uses cases for cutting my teeth on using Zig beyond the toying around I've done recently.
[1]: https://docs.rs/soroban-sdk
[2]: https://github.com/stellar/rs-soroban-env
inet256
-
Show HN: A version control system based on rsync
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.
-
Ask HN: What Are You Working on This Year?
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
-
SourceHut terms of service updates, cryptocurrency projects to be removed
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/
- INET256 is a 256 bit network address space for p2p applications
-
Ask HN: Who Wants to Collaborate?
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.
-
Show HN: Got is like Git, but with an 'o'
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...
- INET256: A 256 bit address space for peer-to-peer applications
-
Spork: Peer-to-peer socket magic in the air
> 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
- INET256: A 256 bit address space for peer-to-peer hosts/applications
What are some alternatives?
bypass-paywalls-chrome - Bypass Paywalls web browser extension for Chrome and Firefox.
platelet - Dispatch system for emergency volunteer couriers.
zfsbootmenu - ZFS Bootloader for root-on-ZFS systems with support for snapshots and native full disk encryption
adama-lang - A headless spreadsheet document container service.
hyperhyperspace-core - A library to create p2p applications, using the browser as a full peer.
ipdr - 🐋 IPFS-backed Docker Registry
fullmoon - Fast and minimalistic Redbean-based Lua web framework in one file.
OpenBazaar - OpenBazaar 2.0 Server Daemon in Go
roqr - QR codes that will rock your world
Phaser - Phaser is a fun, free and fast 2D game framework for making HTML5 games for desktop and mobile web browsers, supporting Canvas and WebGL rendering. [Moved to: https://github.com/phaserjs/phaser]
macrome - The in-tree build system