Farcaster Dev Call starting in 5 minutes!

Farcaster Dev Call starting in 5 minutes! 

https://events.xyz/48b4e0

I'm eth newbie..just learning
(working on @farcaster)

terminally.online

Building @warpcast and @farcaster, new dad, like making food

Technowatermelon. Elder Millenial. Building Farcaster. 

nf.td/varun

question:

im creating a client, and i only want to display through this client the casts that have been written to it. im thinking on adding a database layer that acts as a wrapper of the farcaster data, but im wondering if there is a more efficient way to do it

or maybe some sort of compartimentalization of data that can be helpful in the future (thinking of channels that will have their own apps and probably won't care too much about the protocol as a whole)

wdyt?

cc @horsefacts.eth @deodad

yea most clients will replicate data from hubs into a database

there's an open source package called shuttle that can help with this https://github.com/farcasterxyz/hub-monorepo/tree/main/packages/shuttle

it doesn't support indexing a subset of data so you could either modify it to support this or replicate all data into the database and then index the subset you want for powering your client

definitely recommended

if you want to do things like store reaction counts, quickly render threads, etc you'll need to build indexed data models on top of the raw farcaster data

I'd highly recommend starting with @neynar as they've done a ton of heavy lifting in this area so you can focus on your product instead of infra

can always migrate to your own database later

ok amazing. thank you. i was wondering if adding the database layer in between FC and the client was something that is not recommended to do

i will try with storing each cast on the database as it happens (through this client) and then serving them from there