a16z / awesome-farcaster Goto Github PK

Hubs have come a long way since awesome-farcaster was launched. We should separate out client code, APIs, and Hub implementations.

Ongoing alternative Hub implementations:

• https://github.com/OpenFarcaster/teleport
• https://github.com/withportals/hub-rs

• Findcaster: a new way to discover and browse Farcaster profiles and FIDs. Search by profile field, username, bio, ENS name, and more.

We should have a paragraph that immediately explains and defines Farcaster, Hubble, hubs, clients, etc. to help make the rest of this documentation more legible.

E.g. Instacaster, Pixelpool, and a few others.

We've observed that a significant portion of links within ReadME file repository are outdated, leading to broken references and potentially hindering user experience. This issue impacts approximately 50% of the links.

Outdated links can cause confusion, frustration, and may deter users from engaging with our project effectively. It undermines the credibility of our repository and impedes the accessibility of vital information. Additionally, broken links hinder the seamless flow of navigation, interrupting the user's journey and impeding their ability to access relevant resources.