Content pfp
Content
@
0 reply
0 recast
0 reaction

ted (not lasso) pfp
ted (not lasso)
@ted
the feed feels stale these past 2 weeks with attention on X for trump/biden, lack of anything exciting in crypto (sorry, prove me wrong), ethCC, and general summer offlineness. so plz reply with a hot take or an exciting project or something anything that will give @randomerror.eth’s back a break from carrying us all
25 replies
1 recast
170 reactions

androidsixteen pfp
androidsixteen
@androidsixteen.eth
If you build your core product on the back of service provider startups that haven't been battle-tested or proven themselves, you shouldn't complain when those startups fail and make your product function poorly And it's your job as a founder and the brand behind the product to communicate throughout its lifecycle
3 replies
0 recast
5 reactions

Garrett  pfp
Garrett
@garrett
Soooo what about building on top of Farcaster?
1 reply
0 recast
1 reaction

androidsixteen pfp
androidsixteen
@androidsixteen.eth
What whitelabel products are built on Farcaster? Platform risk is a continuum
1 reply
0 recast
2 reactions

ted (not lasso) pfp
ted (not lasso)
@ted
cc @nonlinear.eth or @jtgi or @slokh or @buoy or @defikaran.eth and any others who have experiencing building on / adjacent to farcaster
4 replies
0 recast
2 reactions

androidsixteen pfp
androidsixteen
@androidsixteen.eth
None of these are whitelabeled
2 replies
0 recast
1 reaction

Garrett  pfp
Garrett
@garrett
Can't think of any whitelabel products built on Farcaster BUT there are a few who have outsourced their social graph or social layer to Farcaster and I think that this is the way that Farcaster likely grows - more apps outsourcing their social graph/messaging layer to Farcaster instead of building it themselves
1 reply
0 recast
0 reaction

androidsixteen pfp
androidsixteen
@androidsixteen.eth
I'm here for that world But in that situation, you would: - vet the protocol and core team, and be sure that it would be built to last - ensure that your customers were protected and communicated with well, especially if you saw signs of incompetence in your dependencies If you do neither, then you're just passing risk to your customer
1 reply
0 recast
1 reaction