Nick T
@nt
could someone explain virtuals to me? one of the most popular coins: $100m market cap robotic, barely interactive AI just 1 person watching live stream (me)
8 replies
1 recast
21 reactions
sean
@swabbie.eth
if you try to actually build on virtuals or ai16z you’ll realize they’re sloppy technologies with toy-level ai kits that only get hype because of token number-go-up
2 replies
0 recast
5 reactions
jp 🎩
@jpfraneto.eth
what technology would you use to set up an agent? im running all my ai locally, so bonus points for support for that
1 reply
0 recast
1 reaction
sean
@swabbie.eth
i tried phidata and even though i decided to just build from scratch, i’d still recommend them. the framework seems solid and the team responds quickly on discord. they also support local models https://docs.phidata.com/models/ollama
1 reply
0 recast
1 reaction
jp 🎩
@jpfraneto.eth
omg this is amazing. if it wasn't for you i would not have ended here why you prefer them to eliza?
1 reply
0 recast
1 reaction
sean
@swabbie.eth
eliza is very limited - you can customize a character json file but if you want to do any more complex agentic flows you might as well build from scratch and not be burdened by that limited framework. the last straw for me was when i realized the character json file was not being used by the framework to select which model to use, rather the framework had a model hardcoded. so, i submitted a PR to have eliza actually read the character file for which model to use, and rather than fix the issue, the ai16z team _hardcoded a different model into the framework_, even responding to my PR that they were "fixing" the problem with the hardcoded solution. just insane behavior by a $1B+ platform. i wouldn't trust them to manage the framework without taking major shortcuts in the future https://github.com/elizaOS/eliza/pull/845
1 reply
0 recast
1 reaction
jp 🎩
@jpfraneto.eth
this is amazing so now you are just doing it yourself? or using phidata?
1 reply
0 recast
1 reaction
