Polynya - Delegate Communication Thread Farcaster id registry, not Warpcast, is the building block we’re incorporating.
Extending this, both, the client and the protocol, are interconnected. In its current form, it’s not possible to promote Farcaster without forcing users to install the app(warpcast). One possible solution could be the use of other client (supercast ??) but again, paying $10/month just for opt-in could be another challenge. Also, even if one has a sponsoring fee and the initial cost of onboarding, installing the app is mandatory which is a bummer for a few I know.
If we want to continue on the same, and I support this, my suggestion would be to use existing solution like Searchcaster via API (example 1 ) or Neynar 1, both easy to build and able to support the expected load.
Running a self-hosted node and feeding data directly from it could be another solution.
Polynya - Delegate Communication Thread Farcaster id registry, not Warpcast, is the building block we’re incorporating.
Extending this, both, the client and the protocol, are interconnected. In its current form, it’s not possible to promote Farcaster without forcing users to install the app(warpcast). One possible solution could be the use of other client (supercast ??) but again, paying $10/month just for opt-in could be another challenge. Also, even if one has a sponsoring fee and the initial cost of onboarding, installing the app is mandatory which is a bummer for a few I know.
If we want to continue on the same, and I support this, my suggestion would be to use existing solution like Searchcaster via API (example 1 ) or Neynar 1, both easy to build and able to support the expected load.
Running a self-hosted node and feeding data directly from it could be another solution.