Terminally Onchain

note to self:

farcaster client ≠ feed of casts

- can be something else that’s useful and still uses the social graph

- need more clients that don’t focus on just content as well. Nook, buoy, and supercast are cooking

- success metric for v1 /toc client should NOT be time spent on app

Open Source and DeAI deep dives at terminallyonchain.xyz

a great prompt for /toc app ideas would be "can it surface *one* piece of onchain content that the /toc community would love to consume every day and facilitate discussion"

- I receive notification.
- I read/watch content.
- I give my thoughts/reply to others.

That's it. Run it back the next day.

Farcaster

Lot of interesting discussions around building on Farcaster lately! Just so we're all on the same page, here's how I think about it:

Farcaster client: main purpose is to consume a feed of casts

Farcaster app: leverages the open social graph and primitives in fun + interesting ways

We need more Farcaster *apps*

Farcaster apps !

https://warpcast.com/zinger/0xd7069a63

definitely not time spent on app, that's the failure of web2 media (and pre-web media) 

we want quality of signal, which, imo, is dependent on reducing time taken to receive and understand the signal

Right, in this post I broke down Farcaster into it's legos and stated that what we consider clients today are Twitter/Reddit-like apps that implement the whole protocol.

There can be much more built beyond these type of clients.

Right, in this post I broke down Farcaster into it's legos and stated that what we consider clients today are Twitter/Reddit-like apps that implement the whole protocol.

There can be much more built beyond these type of clients.

https://paragraph.xyz/@programmista/auth-graphs-feeds-frames