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

dephy-proto

v0.1.3

Published

Protobuf definitions for DePHY messages.

Downloads

2

Readme

Messaging in DePHY

The dephy-proto Package

There are packages for developpers to build applications with protobuf definitions in this repository.

cargo add dephy_proto # for Rust
npm install dephy-proto # for Node.js

The Rust crate is built with prost and published on crates.io.

The JavaScript/TypeScript package for Node.js and Deno is built with pbkit and published on NPM.

Direct Message

A Direct Message in DePHY is a message for DePHY devices and Edge Brokers to communicate directly in Protocol Buffer encoding.

It should be transferred in binary when interacting between the device and Edge Brokers’ service endpoints(MQTT or HTTP).

Usually, a DePHY device send Direct Messages to:

  • mqtt://path.to.dephy.edge:1883
    • topic: /dephy/signed_message
    • the message binary should be the payload
  • http://path.to.dephy.edge:3883/dephy/signed_message
    • method: POST
    • content-type: application/x-dephy
    • the message binary should be the HTTP body

Routed Message

A Routed Message in DePHY is a NoStr event wrapping a Direct Message which will be redistributed by Edge Brokers in a NoStr decentralized network:

  • The kind of the event should be 1111.
  • The content should be a Direct Message encoded in Base58 (a.k.a base58(bytes(SignedMessage))).
  • It should contain these tags:
    • c is the marker of a Routed Message and should be always dephy
    • dephy_from is the DID string of the message sender
    • dephy_to is the DID string of the message recipent
    • dephy_edge is the DID string of the message forwarder

And it looks like this:

{
  "id": "...",
  "pubkey": "...",
  "created_at": 0,
  "kind": 1111, // Magic!
  "content": "...", // base58(bytes(SignedMessage))
  "tags": [
    ["c", "dephy"],
    ["dephy_to", "did:dephy:0x..."], // did(direct_message.payload.to)
    ["dephy_from", "did:dephy:0x..."], // did(direct_message.payload.from)
    ["dephy_edge", "did:dephy:0x..."], // did(origin_edge)
  ],
  "sig": "..."
}

You don’t need to care about Routed Messages if you just build applications interacting with only devices and Edge Brokers.