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

@tool-db/hybrid-network

v1.1.7

Published

Hybrid network adapter for tool-db

Downloads

4

Readme

tool-db-hybrid

The Hybrid network adapter is a mix between bitorrent's tracker-based peer discovery and regular websockets client-server structure.

We use trackers to announce the server via a given name (like a domain or hostname), then clients on a web browser can search for the needed metadata to reach out those servers in the trackers, like a DNS system.

The goal is to be able to reach for any server, anywhere, without going trough censorable channels, removing the most usual points of failure for hosts and allowing servers to move between regions seamlessly, or even having multiple replicas and backups hosted at many places at once.

Future work

Once we identify servers by name we can do all sorts of network schemas, but the most interesting is federations, where clients can choose where to store their data, sign up at those servers and point other users to where their data is stored; Simply using a name like a domain, without caring much about where the server is hosted.

For that to work, document keys should point to a specific server like a route;

manwe-server@:UWGbJslRlXmm5Yi4Ah0x4AlP6na3HEcIhJ7BN-fTCLQHJRQNOSCAG6twTdZ_9VqbWuAZNWaq-ZXrY_A7J64Eyo.data

This, however, should only affect the routing of messages towards specific peers, but not the keys or data itself, so the recieving server will not be awake or the server name portion of the key when recieving it, this way we also allow compatibility between different tooldb modules.