Kash is the flagship interface for interacting with Pulse - inspired by the Akashic Records.

Kash brings all of Pulse's key features together in a single, clean, user interface. This documentation has two sections, the first is a basic setup guide and the second deals with social networking features.

Setup/Basics

Existing tags are added to Kash's context when clicked - the 50 most recent digests will be added:

All of the tags and digests you create in Pulse surface in Kash. Use the "New Tag" button to create a new tag, once you've created it use the "New Digest" button on the next screen to start adding digests.

New tag page
New digest page

If you have other tags digests can be assigned to multiple tags - no single-tag locking here.

All digests, local or federated, can be quickly imported to Kash and discussed using the "ask kash" button:

digest visible in Kash Context

You can also quickly save summaries or quotes from Kash using the (Down Arrow) save summary button to save to the same tag or another tag:

To avoid dumping large numbers of irrelevant digests into Kash's context you can't add a full tag, but the "add results to kash" button will become visible if you search a tag to discuss the results:

Local digests can be selected/searched/grabbed with "select all" for workflow automation once you've configured workflows for the tag:

Note - the same selection mechanism will also work for deletion. To deselect all just hit the "x" next to "delete selected"

Kash for Work/Social Networking


Note: Overmind registration is not required to use Kash's social networking features - but it does provide enhancements. If you are not registered with Overmind this is what you'll be missing:

  • Profile picture in federated tags, portals (audio conferences), and pings (notifications)
  • Automatic matchmaking/content recommendations
  • Node Search based on digest similarity

All of the core functionality will still be there, just without the social profile integration.


If a user creates a digest with an "@" (reply to or tag) to you in a federated tag you'll receive a "ping." To avoid storing creepy data on what you've looked at the read/unread status of pings is stored locally on your device. The Built-in RSS reader works the same way, you can import/export your feeds to move them to other devices. We don't want to know what you're looking at.

Pings (notifications) in federated digests
RSS feeds are stored client-side so that Pulse Inc never knows what's in your feed

In federated tags the interface for replies and @s is similar to websites like Tumblr, Reddit, and 4chan or workplace apps like sharepoint:

Please be aware that any plaintext mention of another user's node name or url in a federated tag will result in a ping - one of our more "fun" design choices for this was making sure that it's hard to say nasty things about people in the same pod as you without them hearing about it. If you want to do that please just make another pod without the person and don't harass them. You are responsible for what you do with your node.

The final social network feature in Kash is "Portals." Portals are audio conferences held on your node with up to 10 speakers and unlimited (currently) listeners. Listeners DO NOT have to be pulse members, all you need to do to have your audience from another platform or another business unit listen in is share the link to the portal that is created when you start it.

To create a portal select the "portals" icon in Kash:

Portals pop-out

Enter a name and description for your portal and click "start portal:"

Once you're in the portal you can share the link in your address bar (which contains the randomly generated portal code) with anyone you'd like to have join by any means you see fit - however, do not share portal links with anyone you don't want listening in. What you do with your node is your responsibility. Pulse is not liable for information spillage as a result of insecure handling of Portal Links, Pod information, etc.

If needed the "x" button on a speaker's profile picture card can be used to immediately demote them back to listener. Further requests for speaker rights can be denied wit a single click.

Registered Pulse users can request to speak after joining your portal and will appear with their node name, profile picture, and bio. Anonymous users may listen but not request to speak. This will not change - please do not report it as a bug or request it as a feature. To maintain high audio quality we cannot provide voip services to non-paying users.