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

microfed

v0.0.12

Published

microfed

Downloads

15

Readme



GitHub license npm npm Github Stars

⚡️ Introduction

This project is still at concept stage and aims to brainstorm the intersection of micro services and the fediverse.

🎨 Design

Microfed follows a modular design approach, ensuring flexibility and maintainability. The high-level design focuses on the interaction between microservices and the fediverse.

The idea is that each component of a fediverse server can be composed from smaller services.

These include:

Design Documentation

✍️ Profile

Your Profile page is the starting point for microfed services. It will generally be an HTTP page, but the data should be agnostic to HTTP or any other protocol so that it can live in a database, or run over a P2P network.

The Profile will be in HTML, with the data in in JSON(-LD). It will contain:

  ✓ The Profile page
  ✓ The User / Actor / Agent
  ✓ Attributes about the User
  ✓ Ability to store a public key
  ✓ A list of connections (friends, knows, followers etc.)
  ✓ Endpoint for Inbox
  ✓ Endpoint for Outbox
  ✓ Authentictation endpoints
  ✓ Arbitrary fields specified by the user

The Profile can be self-hosted, or part of a multi user service. It should be able to run on a mobile device, or in the browser.

Profile Design

📬 Inbox

The Inbox should be a place where people can send messages in JSON. The micro service can filter out messages based on user preferences. The message format should be as far as possible compatible with Activity Pub JSON. Signatures can be used to verify the authenticity of a message.

Inbox Design

📤 Outbox

The Outbox is a service that allows messages to be sent to other inboxes. It should also have to ability to store a private key on behalf of a user, in order to sign outgoing messages. It should be able to route messages to the right endpoints.

Outbox Design

🔐 Authentication

Initially, strong authentication via PKI will be supported. Delegated authentication, such as OAuth and OIDC may be considered desirable. A loosely coupled authentication suite will allow the user to add different authentication modules. This could also work with enterprise authentication.

Authentication Design

⚖️ License

  • MIT