Content pfp
Content
@
https://warpcast.com/~/channel/fc-devs
0 reply
0 recast
0 reaction

Brock pfp
Brock
@runninyeti.eth
Want all of Farcaster free and queryable? Tired of trying to run replicators? We've got a BigQuery dataset for you 😉 https://console.cloud.google.com/bigquery?project=glossy-odyssey-366820&ws=!1m4!1m3!3m2!1sglossy-odyssey-366820!2sfarcaster
8 replies
10 recasts
40 reactions

Brock pfp
Brock
@runninyeti.eth
This dataset is a free, public good and a labor of love from us at indexing.co We're committed to the @farcaster ecosystem 💜 Farcaster is now a first-class citizen for our indexing pipelines right alongside chains like /basese, /syndicate, and /solana Permissionless data == limitless opportunities
3 replies
1 recast
11 reactions

Brock pfp
Brock
@runninyeti.eth
Looking for where to start? Try seeing who the most active reply guys are: https://console.cloud.google.com/bigquery?sq=867429816176:87fef9a0cc334c199363075701d50e74
1 reply
0 recast
3 reactions

Brock pfp
Brock
@runninyeti.eth
Our approach with this dataset is simple: Normalize /hubs events to make data easier to work with. We would *love* feedback to make this as useful for the world as possible To start, we have 5 tables available: casts, links, reactions, verifications, and profiles
3 replies
0 recast
4 reactions

vrypan |--o--| pfp
vrypan |--o--|
@vrypan.eth
I don't see the signer, is it there? The signer is a very important piece of info because it lets you identify the app used to create a message.
2 replies
0 recast
0 reaction

vrypan |--o--| pfp
vrypan |--o--|
@vrypan.eth
I noticed there is a "deleted_at" field. Ideally, there should also be a "pruned_at" field. Not sure how you can get this in an efficient way.
1 reply
0 recast
0 reaction

Brock pfp
Brock
@runninyeti.eth
Curious about your use cases for `pruned_at` 👀 part of our current intent is to provide a long living archive (that isn't constrained by Hubs' pruning)
1 reply
0 recast
0 reaction

vrypan |--o--| pfp
vrypan |--o--|
@vrypan.eth
Messages may be pruned for (at least?) two reasons: storage and signers (when a signer is removed, messages signed with it are pruned). 1. Measure the impact of these two factors (esp after Aug 2024). 2. Understand why a message present in your dataset is not on hubs.
1 reply
0 recast
0 reaction