Dan Romero
@dwr.eth
Why ship Farcaster Pro with just a badge? Why not wait until the other benefits are ready? 1. It’s optional. If you think that’s dumb, you can either wait to subscribe or just skip subscribing completely. 2. For startups, every day you delay something matters. Every time you say “this thing is different and worth delaying” you degrade your one true advantage as a startup: speed. It compounds. And then a few years later when it ultimately doesn’t work out, you likely missed out on something like 100% more opportunities to ship. Action produces information. Your pre-product-market-fit startup is not Apple.
57 replies
106 recasts
736 reactions
shazow
@shazow.eth
Speaking of not delaying, perhaps permissively licensed OSS codebase in 30 days if it sells out? :3
1 reply
0 recast
11 reactions
Dan Romero
@dwr.eth
We’re going to MIT license open source the mobile and web clients this summer. No backend. Like BlueSky does. We will start with a flattened one time and then work our way to continuous release. We won’t accept PRs. Strictly for a reference client. I don’t expect anyone to run a production service with a fork. Too much infra.
6 replies
6 recasts
34 reactions
Stephan
@stephancill
What’s the point of only open sourcing the frontend? Anyone can build a frontend with neynar in like 10 mins
3 replies
0 recast
4 reactions
shazow
@shazow.eth
Hard to tell what the surface area is, we don't know what we don't know. Sooner is better, and open sourcing the frontends is almost definitely easier. Not to mention that this makes the Warplet open source (who wants to use a closed source wallet??).
1 reply
0 recast
5 reactions
Stephan
@stephancill
Sure we’ll see. Most of the parts that interface with the farcaster protocol are on the backend so there isn’t much to reference in this instance of a “reference client” Also not much value in a “flattened” repo when it comes to wallet security since it’s not live code
1 reply
1 recast
1 reaction