Farcaster

What are you most frustrated about re: Farcaster?

If you could change one thing—what would it be and how would you do it?

Working on Farcaster and Warpcast. Longer thoughts at https://dwr.email

two things: 
1- 'fix' the factory so all the sdks built on top of if can update profile data. no privy apps are able to update profile data because of this
2- app namespaces, via that verification of signature's v mentioned during last dev call

Ethereum builder & people connector. Juicebox, Revnet, Defifa & Footy App

It is far less than easy for a 'client side' app to update profile data. The example below reads profiles but no writes. Why? Would love it if there was a an example showing how to writing to a profile using hub-web. A gist is fine but I think this is going to need a lower level PR to get it to work.

There is likely so omission in the Factories causing any sdk that uses those to not support these writes. eg Privy can't/doesn't support profile writes.

It is far less than easy for a 'client side' app to update profile data. The example below reads profiles but no writes. Why? Would love it if there was a an example showing how to writing to a profile using hub-web. A gist is fine but I think this is going to need a lower level PR to get it to work.

There is likely so omission in the Factories causing any sdk that uses those to not support these writes. eg Privy can't/doesn't support profile writes.

https://github.com/farcasterxyz/hub-monorepo/tree/main/packages/hub-web/examples/profile

Namespaces

I’d rather not deal with managing a database and lean toward using decentralized, independently verifiable storage—kind of a “buttless app,” where users have full control of their own data.

That said, things get a bit tricky when an app includes user profile settings (like a favorite soccer club). These settings might be unique to one app or shared across several client apps. For example, The False Nine is interested in finding out readers’ favorite soccer club, which suggests a need for flexible, extensible profile data.

It would be cool if every app had its own space on a hub for profile data. This could even expand to include casts, reactions, and links, all grouped together as what might be called an App Namespace. Since apps sign in on behalf of users, a hub could store data as usual while focusing on the retrieval of information that matters for each specific app. We could use a robots.txt like instruction to guide other apps on how to process the namespace or not

Can you expand on each of these in a full length cast? Not sure I understand either.