Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

distributed-press-social

Package Overview
Dependencies
Maintainers
1
Versions
2
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

distributed-press-social

API for the Distributed Press Social Inbox

  • 1.0.1
  • latest
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
2
increased by100%
Maintainers
1
Weekly downloads
 
Created
Source

social.distributed.press

A Social Inbox for Decentralized Publishing and ActivityPub

How it works

This server runs a minimal implementation of an ActivityPub Inbox and Outbox.

Here's how to use it:

  1. Publish a static site that contains your ActivityPub Actor, Outbox, and Posts. You can fork our staticpub example or use this Jekyll Plugin. Make sure you set up the webfinger endpoint!
  2. Generate a keypair using either OpenSSL or npm run generate-keypair in this repo
  3. Add the public key to your ActivityPub Actor
  4. Set up the social inbox server somewhere like httpa://social.example.com
  5. Note the WebMention compatible format of your account like @username@social.example.com which will be used as the username in parameters
  6. Register your ActorInfo by doing a Signed HTTP POST to /v1/:username/ with JSON that looks like {actorURL, publicKeyId, keypair: {publicKeyPEM,privateKeyPem}} to initialize your inbox. The server will use your keypair to sign HTTP requests for activities you send to your outbox. You can also use the client.setInfo() API.
  7. Set your Actor's inbox property to point at https://yourserver/v1/:username/inbox
  8. Send any Activities you want to notify your followers with by doing a Signed HTTP POST to /v1/:username/outbox

Check out the available API endpoints either in the swagger docs at the https://yourserver/v1/docs/ or in the JS client API in /src/client/index.js.

Development

This project requires Node.js Version 19.x and NPM. The code is written using TypeScript in the src folder which gets compiled into the dist folder.

  • Run server right from the source: npm run dev
  • Lint the code to catch common mistakes and maintain code style: npm run lint
  • Build JS files to dist: npm run build
  • Build and run server: npm run start

Project structure

  • /scripts: Scripts for doing tasks like importing blocklists/admins or generating keypairs
  • /src/ Main folder for source code
  • /src/server/ Source code for the inbox server
  • /src/server/api/ HTTP routes
  • /src/client/ Implementation of a JS client to talk to the inbox via fetch

FAQs

Package last updated on 24 Nov 2023

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc