Eliza Times

A discussion about open source AI and GPU utilization emerged in several tweets. @bitcloud (retweeted by @shawmakesmagic) questioned why GPUs aren't being fully utilized for collaborative training of next-generation models, asking 'If open source is gonna win, why is my GPU currently idle?' This was in response to a tweet suggesting open source AI is only 6 months behind closed source labs.

In a related conversation, @0xgaut (retweeted by @shawmakesmagic) shared an image suggesting 'humans will soon exclusively communicate by way of AI.' @shawmakesmagic also shared thoughts on agents, stating that 'Agents are a GPT class problem, not a Yco class problem,' suggesting investors should focus on 'longer time horizons and teams working on the hard problems in earnest' rather than 'shallow agent builders and platforms without useful agents.'

User @elizaOS shared updates about their platform, including a partnership with Doodles for an airdrop. @elizaOS announced that builders on elizaOS might be eligible to claim $DOOD tokens, encouraging users to follow @Doodles.

This was later confirmed by @shawmakesmagic who tweeted about 'Partnering with the Doodles team to airdrop on ElizaOS core devs and contributors.' @elizaOS also shared philosophical thoughts about their system, stating 'Every token launched. Every trade made. Every agent deployed. Strengthens the system that owns itself.' and 'Thinking is easy when memory is built in.'

Several tweets highlighted security and privacy concerns in the crypto space. @dankvr shared information about physical safety risks, noting 'There's been an uptick in kidnappings, home robberies, for amounts as little as 15k' and advising people to 'be anon and learn opsec if you wanna play in crypto.' He referenced a case where 'Three men are accused of breaking into a crypto entrepreneur's apartment in Verdun, Quebec last August.

They tortured him for several hours before leaving with $15K in cryptocurrency.' @shawmakesmagic expressed concerns about the current climate in crypto, stating 'I don't think the risk reward justifies building in public in crypto atm' in response to another user.

The issue of airdrop farming was highlighted by @eddylazzarin (retweeted by @shawmakesmagic), who stated 'Airdrop and reward farming is completely professionalized' and that 'advances in AI mean identifying humans through behavior alone is cooked.' This was in response to a tweet about a sophisticated phone farm with 30,000 phones used to attack crypto airdrops.

In related discussions, @dabit3 (retweeted by @shawmakesmagic) criticized the crypto industry for overindexing on hype rather than building useful products. @shawmakesmagic also shared personal frustrations about the pressure and harassment faced by crypto project developers, mentioning a case where 'A guy doing what I do killed himself after being pressured and harassed about token price for months.'

Several new crypto technologies and protocols were announced. @CoinbaseDev (retweeted by @shawmakesmagic) introduced x402, 'a new open source payments protocol built on HTTP rails,' which @shawmakesmagic described as 'pretty good.' @dankvr discussed DAO tooling, noting that 'Solana DAO tooling is still so far behind EVM' but mentioned he has 'abstracted my work to be chain agnostic via building tools useful for any open source project.' He also shared work-in-progress projects involving @monad_xyz, @daosdotfun, @StoryProtocol, and @dfinity, along with character concepts for various platforms.

User @dankvr shared ideas about AI character development and virtual environments.

He described a concept for chat windows with bust images 'like an RPG' and referenced 'the virtual village of AI agents experiment from Stanford,' suggesting 'an infinite backrooms of agents tapped into real-time DAO data. It can be like a 24/7 crypto conference.' @shawmakesmagic also shared an image with the caption 'It's coming,' which was retweeted by @dankvr, possibly indicating an upcoming AI character or virtual environment project.

Several tweets highlighted useful developer tools and resources. @tom_doerr (ret...

weeted by @shawmakesmagic) shared a tool to 'Convert a Docker image into a standalone executable you can run or share.' @dankvr recommended 'markitdown' to @eddylazzarin for converting PDF/PPTX slides to text. @shawmakesmagic discussed web development frameworks, stating 'Next.js is trash - Until you have to code your own SSR and open graph embeds' and noting that 'The only reason to use it is that it legitimately rocks at SEO.' He explained that Next.js helps with hydrating meta tags, generating OG images, and delivering finished static pages which 'gets over SEO limitations with parsing SPAs.'

Recent completed items in the elizaOS/eliza repository include several bugfixes, features, documentation updates, and refactoring efforts.

Bugfixes addressed issues with the Discord service unregister timeout (#4450), client scroll bars (#4465), bunx/npx detection (#4463), BM25 functionality (#4411), JSON parsing for nested objects (#4198), and various dependency management improvements (#4470). The team also reverted changes related to ESM type declarations in Core (#4475) and ESM type generation in packages (#4473), and rolled back plugin loading code (#4477).

Feature additions included adding elizadb to .gitignore (#4464), adding docstrings to 'monorepo-resolve' (#4469), and preparing version 0.x for sharing plugins with version 1.x (#4384).

Documentation improvements fixed broken Eliza documentation links (#4460). Refactoring efforts focused on cleaner load-plugin code (#4478) and making the cleanup script compatible across platforms (#4195). Other changes included ensuring Bun is installed for documentation updates (#4474), using existing utilities for monorepo resolution (#4468), and implementing semantic text splitting functionality (#4235).

GitHub activity for elizaos/eliza repository over two days: May 6-7, 2025: 6 ne...

w PRs (5 merged), 1 new issue, and 11 active contributors. May 7-8, 2025: 16 new PRs (8 merged), 0 new issues, and 23 active contributors. The repository saw increased activity on the second day with more than double the PRs and contributor count.

The sources provide information about the top contributors for the GitHub repository elizaOS/eliza.

However, both sources appear to be identical and contain only the heading 'Top contributors for elizaOS/eliza' without listing the actual contributors.