npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@liamcottle/rns.js

v0.0.1

Published

Javascript implementation of the Reticulum Network Stack

Downloads

54

Readme

rns.js

An in-progress, implementation of the Reticulum Network Stack written in Javascript.

This implementation is extremely limited, will likely have breaking changes and is probably not what you should be using.

I am implementing this to learn the RNS stack at the protocol level, while writing it in a language I am very familiar with.

At this stage, I will only be working on the features I want to use, rather than building a complete alternative transport stack.

You should probably look at the official reference stack written in Python;

  • https://github.com/markqvist/Reticulum

What can it do?

  • [x] Create a new Identity
  • [x] Load an existing Identity from Public Keys or Private Keys
  • [x] Connect with a TCPClientInterface to an existing RNS TCPServerInterface
  • [x] Listen for incoming announces
  • [x] Register a Destination
  • [x] Listen for inbound packets to a Destination
  • [x] Send outbound packets to a Destination
  • [x] Send and receive opportunistic LXMF messages over single packets
  • [x] Send and receive direct LXMF messages over an inbound Link
  • [x] Accept inbound Links to a Destination
  • [x] Create outbound Links to a Destination
  • [x] Close Links and listen for when they are closed by the other side
  • [x] Send and receive data packets over an established Link

Examples

There's a few scripts in the examples folder for reference on what currently works.

TODO

  • [ ] Tidy up logic for sending packets and packet types
  • [ ] Implement Link heartbeat packets
  • [ ] Validate LXMF message signatures
  • [ ] Only send packets to relevant interface. Some packets still send to all interfaces
  • [ ] Implement Ratchets
  • [ ] Implement Resources over Links
  • [ ] Support LXMF messages over Link Resources
  • [ ] Support LXMF stamps and tickets
  • [ ] Implement rate limits
  • [ ] Support being a Transport node

References

  • https://reticulum.network
  • https://github.com/markqvist/Reticulum
  • https://github.com/markqvist/Reticulum/wiki/Wire-Packet-Formats
  • https://gist.github.com/liamcottle/e85953bccd6a4f8b436ac4284b29af49

License

MIT