Content
@
https://warpcast.com/~/channel/all-in
0 reply
0 recast
0 reaction
timdaub
@timdaub.eth
Screenshot essay on the two common open source strategies being revealed in today's /all-in podcast
3 replies
0 recast
9 reactions
jamesyoung.eth
@jamesyoung
depends : are you coming at this from a scarcity (finite) or positive sum (growth) perspective
1 reply
0 recast
1 reaction
timdaub
@timdaub.eth
I wouldn‘t say I‘m coming from a scarcity mindset. As I said in the post, I‘m just wondering if knowing how to play the strategies has now become more valuable or if they cease to be valuable assets, in which, I think it‘d make sense to grow into new ones. Is that what you meant?
1 reply
0 recast
1 reaction
jamesyoung.eth
@jamesyoung
scarcity mindset to me means that you move on to new strategies, look for new edge - can’t think of new edge off the top of my mind growth mindset, on the other hand, would mean doubling down and figure out how to leverage contributions - GitHub Oauth in to a smart account and tip $DEGEN to OSS contributors
1 reply
0 recast
1 reaction
timdaub
@timdaub.eth
Here‘s a „my existing knowledge is leverage“ take https://x.com/timdaub/status/1784530561471553938
1 reply
0 recast
0 reaction
jamesyoung.eth
@jamesyoung
open sourcing code is easier to fork and create derivatives (community behind the code is a different story) where models (data) have different open source properties - there is always a dependency on model generation open sourcing data is just lowering development friction and lock-in
1 reply
0 recast
1 reaction
timdaub
@timdaub.eth
Open sourcing model data is lowering lock in? As in, Meta open sourcing Llama 3 is lowering dev lock in? If so, I‘d disagree. The deception of mid devs into thinking that opensource model !== lock in is gonna get many burned badly when Meta is switching from fanning the flames to exstinguishing
1 reply
0 recast
0 reaction
jamesyoung.eth
@jamesyoung
lowering the barrier for vendors to lock-in devs
1 reply
0 recast
1 reaction
