Varun Srinivasan
@v
Miniapp Devs: What are your top 3 requests for us?
27 replies
7 recasts
65 reactions
Lucas | POAP Studio
@gabo
direct cast read / write api
1 reply
0 recast
1 reaction
Daniel - Bountycaster
@pirosb3
Have you seen https://docs.farcaster.xyz/reference/warpcast/direct-casts
1 reply
0 recast
1 reaction
Lucas | POAP Studio
@gabo
yup, thx, the read ie (programatically read the DC received by FID) part is missing to have a full blown messaging system. sadly enough i would guess that is why @base.base.eth had to go xmtp
1 reply
0 recast
1 reaction
KMac
@kmacb.eth
…& the privacy is missing. Thinking about only supporting xmtp for group chats now but fear this will be another time suck if fc (eventually) prioritizes an open private messaging standard of their own- I don’t doubt that will happen. Having more than one to support makes for a very difficult trade off decision. Hoping FC embraces xmtp & makes the decision for all us devs asap
1 reply
0 recast
2 reactions
Lucas | POAP Studio
@gabo
@horsefacts.eth @pirosb3 @dwr.eth great point on direct cast protocol
1 reply
0 recast
0 reaction
Dan Romero
@dwr.eth
DCs have APIs for clients that won't to implement. Feedback from users is Telegram is the app to beat, not Signal.
1 reply
0 recast
2 reactions
KMac
@kmacb.eth
From a miniapp devs perspective, we have a choice to make if we want messaging- pick one or become a group chat inbox aggregator within the not so miniapp. No idea (yet) if fids are used as DIDs. It’s a problem we didn’t need to think about until yesterday. Imagine the ux- come chat about the ⚽️ match, oh wait your on TBA. Fans that use that client have their own group. 🫤 FIP2 solves the non private part of this but creates noise last I checked.
1 reply
0 recast
0 reaction
