Content
@
https://opensea.io/collection/neynar-1
0 reply
0 recast
0 reaction
KMac🍌 ⏩
@kmacb.eth
Does this endpoint include FC profile Location & URL? https://docs.neynar.com/docs/fetching-farcaster-user-based-on-ethereum-address
2 replies
3 recasts
7 reactions
KMac🍌 ⏩
@kmacb.eth
0 reply
0 recast
0 reaction
@
0 reply
0 recast
0 reaction
KMac🍌 ⏩
@kmacb.eth
Exactly. 😆 It’s a wide open field/string that is signed, verified, stored & sync’d. Id advocate for this to be the place for users to share their arbitrary preferences so apps may consume them. People smarter than me prototyped this. @vrypan.eth @livid @haole /furl needs some coordination to not have users stepping on settings that app-b sets when app-a updates the url. versioning needed too … Will use this for Footy app favorite club eg https://ipfs.io/ipfs/QmesuppTqB2ux6YZsCCRNv93wTa3Zqw1WwwXwxRrUeyBVM
3 replies
0 recast
2 reactions
Ghostlinkz
@ghostlinkz.eth
I see what you mean now. If neynar returned the USER_DATA_TYPE_URL, and if someone set that up like you have kmacb.eth.furl.pro, then app devs have a lot more user info to work with
1 reply
0 recast
1 reaction
KMac🍌 ⏩
@kmacb.eth
exactly we'd need some social layer dev concent to honor it or we'll be stepping on each other. A FIP for a JSON format verification at hub that's extensible & version controlled might help. You know what they say though... working code. will fafo
1 reply
0 recast
1 reaction
Ghostlinkz
@ghostlinkz.eth
If the field is there and its not being used, then we must permissionlessly fafo. This is the way!
0 reply
0 recast
1 reaction
