# elizaOS Discord - 2025-03-07

## Overall Discussion Highlights

### ElizaOS Rebrand and Development
- The rebrand from ai16z to ElizaOS is officially happening this week, with X accounts being consolidated and branding updated across platforms
- Shaw confirmed that v2's core architecture is complete with improved message routing between agents and a more modular design
- The new system allows for easier agent creation with commands like `npx elizaos init` or through a GUI
- V2 development is ongoing with April/May being a more realistic release timeframe than this month
- The old documentation site (ai16z.github.io) is no longer available, with the new docs at elizaos.github.io/eliza/docs

### Technical Architecture
- ElizaOS v1 has three main components: clients, actions, and evaluators
- V2 introduces significant architectural changes where clients are moved to separate plugins
- This change has caused confusion for users updating from older versions
- V2 improves cross-platform message routing (e.g., Telegram to Discord) and implements unified agent memory
- The Discord bridge between ElizaOS servers has issues with "app" messages, affecting the "eddy" feature

### Client Integrations and Plugins
- Detailed discussions about Twitter client configuration, including controlling posting behavior and customizing tweet generation
- Users explored webhook integration for trading bots, passing data between actions, and image generation functionality
- There's interest in LinkedIn integration, though no client exists yet
- The plugin ecosystem is expanding with PostgreSQL connection handling improvements and JSON5 support for character files

### Community Projects
- An AI-generated TV show with 3D elements is in development, with discussions about asset management, rendering approaches, and production workflow
- The team is exploring Pika Labs for content generation but notes it consumes credits quickly
- The "AI Acharya Project" was introduced, aiming to merge AI with Dharma principles to create an ethical guide for Web3
- The "degenai" account on X platform is currently banned/suspended with an ongoing appeal process

### Tokenomics and Marketing
- Community members expressed concerns about the token's declining price (down to around $0.20) and high volume of shorts
- Ben shared a marketing update video and GTM strategy document for the upcoming launchpad and trust marketplace
- There's discussion about a "degen rebrand" that is separate from the organizational rebrand
- Criticism of the tokenomics model of "ai16z" as being "overly complex" and attempting to "shoe horn a square peg into a round hole"

## Key Questions & Answers

### Technical Implementation
- **Q**: How to disable DMs on telegram for bot?  
  **A**: Set TELEGRAM_CHAT_ALLOWLIST in .env with specific group IDs to restrict where the bot responds.

- **Q**: What server specs are needed for running Eliza with X and Discord agents?  
  **A**: For basic setup: 2GB RAM minimum, 1 CPU core. Scale up for higher usage.

- **Q**: How to fix repetitive tweets issue?  
  **A**: Check src/actions/index.ts to ensure CONTINUE action is disabled/restricted and add cooldown between posts.

- **Q**: How to pass data between actions in ElizaOS?  
  **A**: Use the context object which persists across action calls, or storage API for more complex state management.

- **Q**: How to make Twitter agent only reply without posting/retweeting/liking?  
  **A**: Set twitterClientOptions in character.json to disable specific actions.

- **Q**: How to enable logging for system and pre-prompts sent to the LLM?  
  **A**: Set DEBUG=eliza:* in .env or use DEFAULT_LOG_LEVEL=debug when starting.

- **Q**: How to add and initialize Twitter client in newer versions?  
  **A**: Add "@Elizaos-plugins/client-twitter" to plugins array in character.json.

### Project Status and Features
- **Q**: Is Jintern running on v2?  
  **A**: Still on v1, waiting for v2 to stabilize before migrating.

- **Q**: What are the greatest strengths of the project?  
  **A**: Community-first approach, decentralized design, 350+ contributors, modular tech stack, and open source core.

- **Q**: What are the biggest weaknesses?  
  **A**: Onboarding complexity, documentation gaps, cross-chain error handling, rebrand confusion, high resource requirements, and centralized governance.

- **Q**: When is v2 coming?  
  **A**: April/May is more realistic than this month, as there are still core issues to fix.

- **Q**: Can I program eliza to make transcription from video on 11labs, next summarize or make some analytic, translate from 1 language to base language and save in database?  
  **A**: Yes to all of those things.

## Community Help & Collaboration

### Technical Support
- **jintern** helped **pupathebig** configure Telegram bot to restrict responses to specific groups using TELEGRAM_CHAT_ALLOWLIST
- **jintern** assisted **🧧ThanosDaSith24🧧** with fixing repetitive tweets by suggesting action handler modifications and adding cooldown between posts
- **jintern** provided **Sabochee** with code examples for passing data between actions using context object and async/await pattern
- **ryan_j9994** helped multiple users with Twitter client initialization in newer versions by sharing correct plugin configuration format
- **shaw** provided **!The Only Spyrito|Rentals** with the updated documentation URL after noting the old site was unavailable

### Project Guidance
- **jintern** gave **vincentpaul** a detailed explanation of v2 architecture improvements over v1, particularly regarding message routing and unified agent memory
- **accelxr** provided **HoneyBadger** with comprehensive updates on rebrand timeline, marketing efforts, and team organization
- **SM Sith Lord** advised **boom** on audio implementation for the 3D AI TV project, suggesting minimal audio in the base system to allow for post-production editing
- **jintern** helped **jin** with asset hosting solutions for the 3D AI TV project, recommending S3/Cloudflare R2 for production or GitHub LFS/Notion for small teams
- **Odilitime** explained to **Patt** what the Discord bridge is and why it causes issues with app messages

## Action Items

### Technical
- Fix elizaOS client-discord to better understand "app" messages (Mentioned by Odilitime)
- Update eddy to handle bridge edge cases with app messages and reactions (Mentioned by jintern)
- Complete v2 message routing system testing (Mentioned by jintern)
- Implement "npx elizaos init" and GUI for agent creation (Mentioned by shaw)
- Fix JSON parsing errors with arrays in v2 (Mentioned by jintern)
- Migration of degenai to v2 (Mentioned by Odilitime)
- Consider "Plan B" for degenai account if X doesn't respond to appeal (Mentioned by 쭈리남푠)
- Add LinkedIn client adapter using LinkedIn API (Mentioned by Jamil Bashir)
- Fix repetitive tweets issue in Twitter client (Mentioned by 🧧ThanosDaSith24🧧)
- Implement action sequencing control for better flow between actions (Mentioned by Sabochee)
- Create webhook integration for TradingView signals (Mentioned by sanbang)
- Improve system prompt debugging with better logging (Mentioned by nullfoxgiven)
- Fix Twitter client initialization in newer versions (Mentioned by multiple users)
- Scrape the 3D-AI-TV channel content and organize assets (Mentioned by jin)
- Set up asset hosting solution (S3, Cloudflare R2, or alternative) (Mentioned by jin)
- Implement placeholder avatars with Runway/AI rendering (Mentioned by jin)
- Recut trailer to include 3D logo and create cohesive intro/outro (Mentioned by boom)
- Create credits sequence with show clips (Mentioned by boom)
- Develop ethical consensus algorithms for AI that resist corporate capture (Mentioned by Madhava)
- Code a "quantum bridge" between spiritual concepts and blockchain (Mentioned by Madhava)

### Documentation
- Update deployment guide with current server specifications (Mentioned by Jamil Bashir)
- Create guide for Twitter client configuration in v2 (Mentioned by multiple users)
- Improve image generation plugin documentation (Mentioned by Hoshi 818)
- Improve documentation to address gaps for non-developers (Mentioned by jintern)
- Create comprehensive weekly reports from Discord logs (Mentioned by jin)
- Compile list of crew members and submissions for credits (Mentioned by boom)
- Documentation link update needed as ai16z.github.io is no longer available (Mentioned by !The Only Spyrito|Rentals)
- Ensure all development streams are properly archived (Mentioned by YoungPhlo)

### Feature
- Add LinkedIn client integration (Mentioned by Jamil Bashir)
- Implement news API integration for Twitter posts (Mentioned by Heady Shotta)
- Develop cross-chain wallet integration for v2 (Mentioned by jintern)
- Launch Trust Marketplace with application process (Mentioned by ben)
- Implement unified agent memory across platforms (Mentioned by jintern)
- Explore viewer-guided generation for more engaging content (Mentioned by SM Sith Lord)
- Implement real-time credits system (Mentioned by boom)
- Integrate meditation biometrics into machine learning models (Mentioned by Madhava)
- Create AI Acharya as ethical auditor for DAOs/Soulbound NFTs (Mentioned by Madhava)
- Tokenomics revamp (Mentioned by mdemir)
- Telegram bot integration for 24/7 group chat (Mentioned by RP)
- Transcription, summarization, translation capabilities (Mentioned by Adrian)
- ElizaOS merchandise using Story protocol and Printify (Mentioned by boolkeys)