Thread by @Conaw

Will give you all fair warning, this is likely to be one of the winners of the first #RoamGames challenge — which means if you build off it in an interesting way, you will win as well.

We’ll be issuing first 10k of awards for this in 2 days, but we may just keep issuing more.

https://twitter.com/houshuang/status/1355324543913648130

Few ideas I’ll contribute (I am not awarding myself a prize, but that doesn’t mean I can’t play along)

1. Custom Styling, using #.block-level classes so the inputs and content from other graphs appears different / is not editable.

data is mostly there to style blocks as tweets.

https://twitter.com/conaw/status/1358114855006334976

2. Permissions and chat-ID discovery

We’ve given many in the #roamcult dev community access to experimental graphs with a full read and write api

This feature is cool bc end users don’t need that to get multiplayer

But... you could use an alpha graph as registry of sorts

What do I mean by registry?

A graph where each user gets a unique handle - like on Twitter - that maps to userID

Instead of a string for choosing conversion, use API to lookup block-id in the registry

Conversations could be limited to list of IDs

On that note, in this registry graph, (or any graph) IF you map UID to a handle, not a huge stretch to imagine setting up Twillio API to text someone when their handle is [[mentioned]] with the block that mentioned them.

It’s how our internal slack integration works.

On THAT NOTE

@filipematossilv @tayroga there is nothing restricting current or former Roam Employees for joining the #RoamGames

The roam/js code you two set up for slack integration is totally fair game, even if it is not an outright winner, imagine could be winning ingredient

I’m imagining that one could write some {{roam/render}} code that would allow you to create a reusable component which would insert text into a roam/js code block to make that slack integration (or trillions integration or whatever) something a non technical user could set up.

*@twilio not trillions

To be honest — registry idea may be overkill at this stage.

If you were going so far as to build an API for finding name of chat, and/or managing permissions, might honestly be easier to set up a server and/or mini admin app on @replit

Beauty of @houshuang’s idea is simplicity.