This is a Lerna monorepo that holds packages related to an implementation of the ActivityPub protocol specification.
ActivityPub is a standardized method of exchanging social data.
This project is still incomplete at the moment. Much of the core functionality is complete, but refer to:
Canonical example using Express, MongoDB, Firebase Auth, JSX:
(async () => {
const app = express();
// Firebase Authentication adapter.
const firebaseServiceAccount: ServiceAccount = JSON.parse(decodeURIComponent(process.env.AP_SERVICE_ACCOUNT));
const firebaseAuthAdapter =
new FirebaseAuthAdapter(
firebaseServiceAccount,
'firebase-project-id'
);
// Mongo DB adapter.
const mongoClient = new MongoClient(process.env.AP_MONGO_CLIENT_URL);
await mongoClient.connect();
const mongoDb = mongoClient.db(process.env.AP_MONGO_DB_NAME);
const mongoDbAdapter = new MongoDbAdapter(mongoDb);
// Server-to-Server Delivery adapter.
const defaultDeliveryAdapter =
new DeliveryAdapter({
adapters: {
db: mongoDbAdapter,
},
});
// FTP Storage adapter.
const ftpStorageAdapter =
new FtpStorageAdapter(
JSON.parse(decodeURIComponent(process.env.AP_FTP_CONFIG)),
'/uploads'
);
const renderLoginPage = async () => {
return `
<!doctype html>
${renderToString(
<LoginPage />
)}`;
};
const renderHomePage = async ({ actor }) => {
return `
<!doctype html>
${renderToString(
<DashboardPage actor={actor} />
)}
`;
};
const renderEntityPage = async ({ entity, actor }) => {
return `
<!doctype html>
${renderToString(
<EntityPage
entity={entity}
actor={actor}
/>
)}
`;
};
app.use(
activityPub({
pages: {
login: renderLoginPage,
home: renderHomePage,
entity: renderEntityPage,
},
adapters: {
auth: firebaseAuthAdapter,
db: mongoDbAdapter,
delivery: defaultDeliveryAdapter,
storage: ftpStorageAdapter,
}
}),
);
app.get('/', (req: IncomingMessage, res: ServerResponse) => {
const indexPage = `
<!doctype html>
${renderToString(
<IndexPage />
)}
`;
res.statusCode = 200;
res.setHeader('Content-Type', 'text/html')
res.write(indexPage);
res.end();
});
app.listen(process.env.PORT ?? 3000, () => {
console.log('Running...');
});
})();This project aims to be spec-compliant.
This project aims to be an non-opinionated as possible, providing abstracted layers that can hopefully work with any Node.js project.
This project is MIT-licensed, with the hope it will be forked, reused, or wholly included in other projects due to this permissive license. There may be similiar software that exists, but inclusion would be inviable due to licensing restrictions.
There are a few use cases this project attempts to fulfill. Ideally this project papers over some of the complexity of JSON-LD, Activity Streams collections, etc. to make getting started easy.
Someone already has an HTML blog and a domain name and wants their posts to be read by others and get replies. Instead of setting up a CMS, they decide to set up an ActivityPub server.
An exercise app wants to build in social features to make their users feel proud of their achievements. This would probably include something like a notification bell and a feed where updates about their friends appear. Users might have with the option to react with an emoji or sticker.
All these exchanges would stay local to the server.
A small group of people who communicate online become dissatisfied with their existing app's policies and decide to communicate privately. They would like to develop their own system for communication.
Although ActivityPub does not define an encryption layer, messages could stay local to a single server or could be exchanged between all parties in an ephermeral way. Encryption could be a good addition, however.
Ideally this project could be used to build an entire social network that interfaces with the rest of the Fediverse.
This project aims to be agnostic as to how the data is stored, which server is used, etc. Adapters that conform to a specific interface can be mixed and matched.
Additionally, plugins can modify the endpoints.
The logic layer that get included in all projects include these packages:
activitypub-core-types- The Activity vocabularies converted to TypeScript types.
activitypub-core-endpoints- The logic for carrying out the bulk of the ActivityPub protocol.
activitypub-core-delivery- The logic specific to the Server-to-Server delivery (federation).
activitypub-core-utilities- Common functions with no dependencies on packages from upper layers.
There is a large amount of data related to profiles and interactions that must be persisted over time.
Currently this project comes with:
activitypub-core-db-mongo
- TODO: SQLite, PostreSQL
Users can sign up and log in to their account.
Current this project comes with:
activitypub-core-auth-firebase
- TODO: Passport.js
Allows for users to upload media, such as profile pictures or attachments.
Currently this project comes with:
activitypub-core-storage-ftp
- TODO: AWS S3, Firebase Storage
The server must handle the core endpoint requests.
Currently this project comes with:
activitypub-core-server-express
- TODO: Fastify, Next.js
In progress.
Injectables that can modify core functionality.
Currently this project comes with:
activitypub-core-plugin-foaf
TBD. Currently using JSX (React) server-side.