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

activity-engine

v0.0.2-alpha

Published

WARNING: This project is still in alpha, use with caution.

Downloads

4

Readme

node-activity-engine

WARNING: This project is still in alpha, use with caution.

A nimble and follower aware fan out activity stream framework that uses Redis as backend.

Why?

Activity streams are a major part of how people consume information on the web today. Twitter's timeline is an activity stream where the activities are tweets and they are ordered by time, Facebook's news feed is an activity stream ordered by EdgeRank. This framework is for managing such activity streams abstracting away they nitty-gritty of routing activities to the right stream and ordering them.

This framework was inspired by the talk "Timelines @ Twitter" given by Arya Asemanfar.

Example

https://github.com/olahol/node-activity-engine/blob/master/examples/twitter.coffee

Concepts

Activity

A unique identifier, should usually be a key pointing to a database row (for example a primary key in a SQL table).

Activity stream

A list of activities ordered by their score (default score is time).

Entity

Something that performs or receives activities, a user, a group, a tag, an image etc. All entities have two activity streams, a sent activity stream which consists of its own activities and an inbox activity stream which consist of the activities of the entities it's following. Like an activity an entity should usually be a key pointing to a database object, show that metadata can be retrieved.

Following

An entity can follow another entity, which means it will be routed activies from that entitiy.

API

Engine.sent(entity, offset, take, cb(err, activities))

Engine.inbox(entity, offset, take, cb(err, activities))


Engine.post(entity, activity, cb(err))

Engine.put(entity, activity, cb(err))

Engine.spread(entity, activity, cb(err))


Engine.unpost(entity, activity, cb(err))

Engine.unput(entity, activity, cb(err))

Engine.unspread(entity, activity, cb(err))


Engine.follow(from, to, cb(err))

Engine.subscribe(from, to, cb(err))

Engine.sprinkle(from, to, cb(err))


Engine.unfollow(from, to, cb(err))

Engine.unsubscribe(from, to, cb(err))

Engine.nub(from, to, cb(err))