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?

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

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

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

the barrier for apps (especially frames) to write back to the network is too high

i would make a cast intent accessible from within frames, similar to viewProfile

i'm excited about the prospect of app keys going on snapchain and becoming free. with that being said there's also a big opportunity to overhaul the way app keys work with snapchain. would love to see the following
- ability for frames to easily get write access
- ability for signers to expire (by default preferably)
- ability to revoke a signer without deleting all messages (this is not intuitive behaviour)
- bonus: only write specific types of messages (e.g. user data, reactions, casts, links) and maybe the ability to write x times per day

@dwr.eth flexible user data types would be a big unlock for interoperability between apps. for example, the footy frame could expose the user's favourite team in a user data message which i could use in my irl frame to allow supporters to view eachothers' posts

would love to see flexible reaction types too. would let apps experiment with different (interoperable!) views of the farcaster data e.g. downvotes, moderation signals, etc

the uptake of all of this is heavily dependent on making it easier for apps to write back to farcaster (https://warpcast.com/stephancill/0xcf27b90f)