Dan Romero
@dwr.eth
Channel Leads We're going to try an experiment for the next 6 weeks. For 20 or so channels, we're going to have a *lead*. I'm going to be working with this group to try to significantly increase quality casts and engagement in their channels. If you're interested in applying: https://forms.gle/LYsuqsofMR24LF3b9
36 replies
44 recasts
138 reactions
vincent
@pixel
> Warpcast plans to deprecate API > Channel data (mapping between parent_url and channel names in Warpcast clients) aren't exposed to public Seems like an important data for the community since this is the canonical channel we all use. Do you have any thoughts on this?
2 replies
0 recast
0 reaction
Greg
@greg
You can find the parent_url of any cast from the protocol, then manually map it to a Warpcast channel name with a tiny bit of work (search the cast of 1 hash per channel in your db). 3rd parties can also keep it organized https://github.com/neynarxyz/farcaster-channels/blob/main/warpcast.json
1 reply
0 recast
0 reaction
vincent
@pixel
yeah, thing is the mapping between parent_url <-> channel_id is still taken from Warpcast API, or am I missing something? that repo is possible because it's taking data from Warpcast, unless I'm missing something...
1 reply
0 recast
0 reaction
Greg
@greg
hmm I haven’t used the Warpcast APIs channel endpoints What’s the purpose of the channel_id? I’m guessing just a pretty URL? In what context does that matter when building external apps?
1 reply
0 recast
0 reaction
