Neynar
/neynar13320
The easiest way to build on Farcaster | neynar.com | @neynar
"Show more replies"-style conversations are now easier to build than ever before!
Using the new 'fold' option in the conversation api, you can now specify 'above' or 'below'. Cast replies can remain unified as well by not using this new option.
- API: https://docs.neynar.com/reference/cast-conversation
- SDK: lookupCastConversation() https://github.com/neynarxyz/nodejs-sdk/blob/main/src/neynar-api/neynar-api-client.ts#L1333-L1429
Happy building! 🪐
Using the new 'fold' option in the conversation api, you can now specify 'above' or 'below'. Cast replies can remain unified as well by not using this new option.
- API: https://docs.neynar.com/reference/cast-conversation
- SDK: lookupCastConversation() https://github.com/neynarxyz/nodejs-sdk/blob/main/src/neynar-api/neynar-api-client.ts#L1333-L1429
Happy building! 🪐
outage
investigating
investigating
gm @neynar team :-)
Could you add the "external_link": { "title": "Join", "url": "https://www.some.com" } field to channel data in https://api.neynar.com/v2/farcaster/channel
Thanks a lot !
Could you add the "external_link": { "title": "Join", "url": "https://www.some.com" } field to channel data in https://api.neynar.com/v2/farcaster/channel
Thanks a lot !
Is there a bug in the neynar api?
According to the api I have 8k followers? But according to Warpcast and Airstack I have 4.7.
According to the api I have 8k followers? But according to Warpcast and Airstack I have 4.7.
In case you need a simple way to search for a cast:
The `viewer_context` for users now shows whether the viewer is blocking, blocked by, or has *muted that user.
In most endpoints, these fields will always be false, but in endpoints where mutes and blocks aren't filtered, these fields can be true. See below for an example from the user/bulk endpoint. https://docs.neynar.com/reference/user-bulk
Happy Farcaster Friday! 🪐
In most endpoints, these fields will always be false, but in endpoints where mutes and blocks aren't filtered, these fields can be true. See below for an example from the user/bulk endpoint. https://docs.neynar.com/reference/user-bulk
Happy Farcaster Friday! 🪐
How can you pull a list of followers and members from a channel?
If you're using go_neynar_sdk and are wondering how to generate a signer in Go, cc @jpfraneto.eth this repo should help you, will add an endpoint in a few hours that shows how to use the sdk if you don't want to create the signer yourself
https://github.com/atlasmoth/go_farcaster_signer
https://github.com/atlasmoth/go_farcaster_signer
here are the full notes from today's biweekly farcaster dev call, live on the neynar blog!
TLDR:
Channels iterations are underway, Direct Casts shipped auto-updating messages and are working on new APIs, the Hub team has been looking at a memleak bug, Location FIPs and Warpcast Twitter verifications are coming, and Warpcast is investigating smart wallet/multi-client support for SIWF
https://neynar.com/blog/fc-dev-call-101024
TLDR:
Channels iterations are underway, Direct Casts shipped auto-updating messages and are working on new APIs, the Hub team has been looking at a memleak bug, Location FIPs and Warpcast Twitter verifications are coming, and Warpcast is investigating smart wallet/multi-client support for SIWF
https://neynar.com/blog/fc-dev-call-101024
taking live notes from today's(back on regular schedule) biweekly farcaster dev call
here's an overview of the top priorities from warpcast, which they'll give updates on (ranked in order):
1. Growth(Channels and Frames updates)
2. Direct Casts
3. Reducing Sign Up Costs
4. Hubs
5. FIP: Locations
6. Sign In with Farcaster
https://warpcast.com/v/0x295c90b5
https://warpcast.notion.site/Oct-10-2024-11a6a6c0c101806697ebcf6a9fb3852b
here's an overview of the top priorities from warpcast, which they'll give updates on (ranked in order):
1. Growth(Channels and Frames updates)
2. Direct Casts
3. Reducing Sign Up Costs
4. Hubs
5. FIP: Locations
6. Sign In with Farcaster
https://warpcast.com/v/0x295c90b5
https://warpcast.notion.site/Oct-10-2024-11a6a6c0c101806697ebcf6a9fb3852b
By popular request, you can now fetch all channels a user is a member of!
Data currently has about a ~1 hour lag
Via API: https://docs.neynar.com/reference/user-channel-memberships
Via SDK: fetchUserChannelMemberships() https://www.npmjs.com/package/@neynar/nodejs-sdk/v/1.60.0
Happy building 🪐
Data currently has about a ~1 hour lag
Via API: https://docs.neynar.com/reference/user-channel-memberships
Via SDK: fetchUserChannelMemberships() https://www.npmjs.com/package/@neynar/nodejs-sdk/v/1.60.0
Happy building 🪐
Improvement to the dev portal: you can now see usage by app!
Use this to further help manage your compute unit usage
Check it out at https://dev.neynar.com!
Use this to further help manage your compute unit usage
Check it out at https://dev.neynar.com!
Hey guys, is there an endpoint to fetch all channels that user is a member of?
Adding to my wishlist : Pin / Unpin API with announcement 🙏🏻
(higher priority than the cast moderation api for me)
(higher priority than the cast moderation api for me)
@neynar made us able to pass another milestone with @anser-social.eth that would have cost twice as much if we were not using them.
@farcaster would not be at the state it is now without them abstracting the network complexity and enabling builders to iterate fast.
Kudos to the team !
@farcaster would not be at the state it is now without them abstracting the network complexity and enabling builders to iterate fast.
Kudos to the team !
webhooks seeing issues, missed events will be fired once resolved
PS - bad week for network stability, working through hub stability and workflows depending on it
PS - bad week for network stability, working through hub stability and workflows depending on it
It's now possible to sort conversations by engagement!
As an extra bonus, this new functionality makes it easier to render threads by the same author more easily.
How?:
There's a new "sort type" optional argument. If you set it to "algorithmic" you can get the new behavior.
Under the hood, the algorithm does two main things:
- Return replies by the original author first in the list
- Then, sort replies from other authors by engagement
Check out the docs here: https://docs.neynar.com/reference/cast-conversation
Try it out!
API: /v2/farcaster/cast/conversation?sort_type=algorithmic
SDK: lookupCastConversation(/* args */, { sortType: 'algorithmic' })
Happy building 🪐
As an extra bonus, this new functionality makes it easier to render threads by the same author more easily.
How?:
There's a new "sort type" optional argument. If you set it to "algorithmic" you can get the new behavior.
Under the hood, the algorithm does two main things:
- Return replies by the original author first in the list
- Then, sort replies from other authors by engagement
Check out the docs here: https://docs.neynar.com/reference/cast-conversation
Try it out!
API: /v2/farcaster/cast/conversation?sort_type=algorithmic
SDK: lookupCastConversation(/* args */, { sortType: 'algorithmic' })
Happy building 🪐
Interesting edge cast in the API to get a cast from a warpcast URL.
If the user had a fname, and then switched to an ENS username, the API returns 404 on URLs that use the fname.
For example : https://warpcast.com/scryptoguy/0x30a5586f
If the user had a fname, and then switched to an ENS username, the API returns 404 on URLs that use the fname.
For example : https://warpcast.com/scryptoguy/0x30a5586f
As channel changes go live tomorrow, here's 3 key things re: Neynar APIs
1. feed/channels API will default to showing casts from channel members only https://docs.neynar.com/reference/feed-channels ,there will be a flag to toggle this off if needed
2. feed/parent_urls API will show what's on the protocol so there's still a way to get raw protocol data for something that's not a warpcast channel
3. channel/member APIs are already live: https://docs.neynar.com/reference/list-channel-members
reach out with any questions 🪐
1. feed/channels API will default to showing casts from channel members only https://docs.neynar.com/reference/feed-channels ,there will be a flag to toggle this off if needed
2. feed/parent_urls API will show what's on the protocol so there's still a way to get raw protocol data for something that's not a warpcast channel
3. channel/member APIs are already live: https://docs.neynar.com/reference/list-channel-members
reach out with any questions 🪐
Here are the full notes from today's /fc-devs call, live on the Neynar blog!
Merkle made it clear that their key priorities right now are:
1. Channels
2. Frames / Mini Apps
3. Programmable DC’s
4. Hubs Scalability
5. Location
https://neynar.com/blog/fc-dev-call-100324
https://warpcast.com/dylsteck.eth/0xd9f4ca1c
Merkle made it clear that their key priorities right now are:
1. Channels
2. Frames / Mini Apps
3. Programmable DC’s
4. Hubs Scalability
5. Location
https://neynar.com/blog/fc-dev-call-100324
https://warpcast.com/dylsteck.eth/0xd9f4ca1c
ga, taking live notes from today's biweekly /fc-devs call!
seems like the main agenda is to go over the top priorities, which are
- growth(through frames and channels)
- direct casts
- reduce sign up costs
- hubs
- fip: locations
- sign in with farcaster
will run a dev call next week too and then back to the biweekly schedule(thrown off bc of dev day last week)
https://warpcast.com/v/0x2b5a21b8
seems like the main agenda is to go over the top priorities, which are
- growth(through frames and channels)
- direct casts
- reduce sign up costs
- hubs
- fip: locations
- sign in with farcaster
will run a dev call next week too and then back to the biweekly schedule(thrown off bc of dev day last week)
https://warpcast.com/v/0x2b5a21b8
our webhook fires are backlogged, actively investigating
all backed up events will be fired once resolved
all backed up events will be fired once resolved
if you provide a `viewer_fid` in any of our APIs, all blocks by the user will automatically be respected
nothing additional needed
react out if any questions 🪐
nothing additional needed
react out if any questions 🪐