Let's #build on the #idea of multi-chain #social hubs... Thanks to @mattb.near, #builders can use a modular SDK to build Lens apps on the blockchain operating system. Check out V2 of his [LensSDK](https://near.org/mob.near/widget/WidgetSource?src=sdks.near/widget/SDKs.Lens.LensSDK), and follow him to learn more about building new and improved #SDKs for everyone #OpenWeb > Learn more: @sdks.near ([GitHub](https://github.com/NEARBuilders/sdks.near)) *p.s. #question about a project called [Nearcaster](https://everything.dev/james.near/widget/nearcaster)* ### What is wrong with this [example code](https://near.social/mob.near/widget/WidgetSource?src=james.near/widget/nearcaster)? --> built using the Neynar API to interact with Farcaster ``` function fetchData() { const params = { target_fid: targetId, // 195725 viewer_fid: viewerId, // 235259 }; const urlSearchParams = Object.keys(params) .map((param) => `${param}=${params[param]}`) .join("&"); let promise = asyncFetch( `https://api.neynar.com/v2/farcaster/followers/relevant?${urlSearchParams}`, headers ); promise.then((data) => { setFarData(data); }); } ``` ### CONTEXT The **objective** is to merge Near Social graphs with [Lens](https://www.lens.xyz), [Farcaster](https://www.farcaster.xyz), and other decentralized ecosystems. The **plan** is to fork this `SocialGraph` visualization, originally [created](https://near.social/mob.near/widget/VotersGraph) by @mob.near and further [adapted](https://near.social/efiz.near/widget/SocialGraph) by @efiz.near. Once we have a way to get lists of connected accounts, I'll work on integrating other APIs to evolve this common resource. This exploration can generate opportunities for successful projects and communities involving Lens and Farcaster, as well as Near Social. ### ISSUE Using the [Neynar API](https://neynar.com)—which is awesome—my widget is not getting any data from this endpoint: `api.neynar.com/v2/farcaster/followers/relevant` ([docs]( https://api.neynar.com/v2/farcaster/followers/relevant)) Matt already solved a problem with the API call parameters not being configured properly as `urlSearchParams`. Now I'd assume there is just a dependency missing from the #BOS environment. Neynar's [Getting Started](https://docs.neynar.com/docs/getting-started-with-neynar) doc mentions installing the SDK: `@neynar/nodejs-sdk` ***Note:** A cool thing about Farcaster is performance, since only signatures and identity pieces are on-chain. However, it seems like running a [hub](https://docs.farcaster.xyz/learn/architecture/hubs) is necessary to interact with their P2P infrastructure.* ### SUMMARY I'm still not sure why that endpoint is not working in the BOS environment. I'll try running a client using [Hubble](https://www.thehubble.xyz), which is their main template. I guess a tricky part will be integrating the custom elements with a gateway, similar to how @every.near added support for [tldraw](https://draw.everything.dev) and [Livepeer](https://everything.dev/?page=video). > [everything.dev](https://everything.dev) ([GitHub](https://github.com/near-everything/viewer)) ### OPEN REQUEST Help me figure out how to build on [this amazing #resource](https://github.com/petersalomonsen/near-bos-webcomponent) by @petersalomonsen.near for embedding BOS content as a web component. Please reply here with any feedback. Thank you! ### PICTURED Below is the official [architecture diagram](https://docs.farcaster.xyz/learn/architecture/overview#architecture) of Farcaster, which may benefit from accessible, secure, and composable widgets built on #NEAR. Let me know what you think.