tony
Week 49 25
16
Week 48 25
53
Week 45 25
9
Week 44 25
2
Week 37 25
1
Week 19 25
1
Week 51 24
1
Week 41 24
2
Week 25 24
1
Week 20 24
2
Week 13 24
1
Week 11 24
1
Week 09 24
1
Week 08 24
1
Week 07 24
2
Week 06 24
1
Week 03 24
3
Week 02 24
4
Week 01 24
7
Week 52 23
7
Week 51 23
5
Week 50 23
7
Week 49 23
3
Week 48 23
4
Week 47 23
7
Week 46 23
9
Week 45 23
10
Week 44 23
7
Week 43 23
5
Week 42 23
7
Week 41 23
8
Week 40 23
10
Week 39 23
10
Week 38 23
22
Week 37 23
5
Week 36 23
1
Week 34 23
2
Week 32 23
1
Week 28 23
1
Week 25 23
1
Week 24 23
1
Week 21 23
2
Week 20 23
1
Week 19 23
3
Week 18 23
6
Week 17 23
1
Week 16 23
2
Week 15 23
5
Week 14 23
5
Week 13 23
1
Week 12 23
7
Week 11 23
10
Week 10 23
2
Week 09 23
1
Week 08 23
4
Week 07 23
2
Week 05 23
1
Week 04 23
4
Week 03 23
1
Week 02 23
2
Week 01 23
9
Week 52 22
5
Week 51 22
3
Week 50 22
19
Week 49 22
3
All Posts Articles Meeting Notes
Mini JS
Base Styles
tonyennis.com
Atlas
Updates.fm
Copybot
Week
49
Updates.fm
Dec 10
Permalink Edit
Delete

  • Context: I just built a tool called Streams, which lets me send emails from Roam. You'll probably start receiving some of these emails, so I wanted to explain the rationale behind them.

  • Background

  • "Streams" is a simple product I built to enhance my daily use of Roam. I use Roam to keep track of and record everything I'm doing throughout the day. Often the notes I take are relevant to other members of the team, and sharing them would be beneficial. If I think of it, I'll take a screenshot and pop it in Telegram, but 1. That's often clunky, and 2. Once shared, particularly in a group, the messages tend to get lost in the noise.

  • The ability to streamline sending group updates that actually get read, and that have a clear uninterrupted timeline that can be looked backed over, is something I've been wanting to find a solution to for a while. This feature set is very similar to any email newsletter tool, whose core functions are 1. Create a permalink for each post, and 2. Broadcast an email to specified subscribers. The tools I've tried so far are Asana Project updates and Circle.so - both have the ability to post an update that gets sent to subscribers. But neither worked because they weren't tools that I regularly used as part of my workflow, so there was always friction going there specifically to post updates.

  • Considering the fact that I already use Roam for several hours a day, and have it organized by Project with updates anyway, using Roam for this is the obvious option. So I just built out a quick prototype to test, the first part of which I've just completed.

  • Here's how it works

  • There's a backend where I can set up "Streams" and add subscribers. As of right now, I have a stream for ProHeadshots, a stream for VanBuild, and a stream for Streams (how meta).

  • Once a stream has been created it gets its own webhook. This webhook can be called super easy directly from Roam (using the Postman API).

  • Now, whenever I create a project heading in Roam, the section header has a little icon button on it. When I click that button, all the contents of that section get sent over to Streams. Streams will then create a "post" or page for that content, and send an email to anyone who's subscribed to that stream.

  • I'll create a more detailed explanation and Loom at some point. For now, I'll spend a few weeks seeing where the behaviour sticks.