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

@vowlink/protocol

v5.4.0

Published

VowLink Protocol implementation

Downloads

47

Readme

VowLink

Build Status IRC Channel License

VowLink is a protocol for building "Distributed Secure IRC" (or distributed Slack if you wish). The core principles are:

  • No server required
  • Untrusted parties help distribute messages
  • Invites reveal messages to new participants
  • The "invite chain" involves 3 people or less
  • Write access expires after 99 days.

NOTE: The protocol is still under development. Breaking changes will be avoided whenever possible.

Trying it out

The Desktop Client is a great way to start using the protocol with your peers. Once installed the identities and channels can be created. Once requested an invite to other's channel, or approved an invite for someone else the familiar UI (:wink:) will help to make the conversation over a P2P network.

screenshot

Protocol

The Protocol and all repositories in GitHub organization are Open Source (MIT Licensed). Aside from other benefits this means that a custom client can connect to the network. VowLink is not a walled garden.

Usage

Initialization (requires sodium-universal or any other library with compatible API):

import * as sodium from 'sodium-universal';
import VowLink, { Message, StreamSocket } from '@vowlink/protocol';
import SqliteStorage from '@vowlink/sqlite-storage';

// Initialize persistence layer
const storage = new SqliteStorage({
  file: 'db.sqlite',
  passphrase,
});
await storage.open();

// Initialize protocol layer
const vowLink = new VowLink({
  sodium,
  storage,
  passphrase: 'secret',
});
const isRightPassphrase = await vowLink.load();
if (!isRightPassPhrase) {
  throw new Error('Invalid passphrase');
}

// Create identity (and associated channel)
// NOTE: multiple identities/channels are supported
const identity = await vowlink.createIdentity('identity-name');
const channel = vowlink.getChannel('identity-name');

See @vowlink/hyperswarm for details on connecting to remote peers and requesting/issuing invites.

Process incoming messages (and similarly outgoing with waitForOutgoingMessage:

function loop() {
  const wait = channel.waitForIncomingMessage();
  wait.promise.then((message) => {
    // Display message
    loop();
  });

  // Call `wait.cancel()` if needed
}
loop();

See promise-waitlist for waiting APIs here and in later code samples. waitForUpdate could be used to refresh the channel contents.

Post a new message:

const author = identity;
await channel.post(Message.json({ /* any json data here */ }), author);

Display channel messages:

// Get the latest 100 messages
const messages = await channel.getReverseMessagesAtOffset(
  0, // end of the message list
  100 // limit
);

for (const message of messages.slice().reverse()) {
  const displayPath = message.getAuthor().displayPath;

  const text = message.isRoot ? '<root>' : message.json.text;

  console.log(`${displayPath.join('>')}: ${text}`);
}

Create read-only channel using its public key obtained elsewhere:

cosnt feed = await vowLink.feedFromPublicKey(
  publicKey,
  { name: 'channel-name' });

Help requested

The protocol draft and the implementations are in the very early stages. Any feedback or ideas on boths are very appreciated.

Not exhaustive list of possible issues:

  • Unclear wording in the protocol description
  • Cryptography problems
  • Bugs in implementation
  • API improvements
  • Documentation!

Community

LICENSE

This software is licensed under the MIT License.

Copyright Fedor Indutny, 2019.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.