hi. im interested in digitizing all the Epstein files into vector format and then reference training it with a LLM model. After that I want to convert and tag the data into markdown files that would be easily searchable via visual mind maps and context search. this is a volunteer type project, meaning no money involved but this would look great on a resume, portfolio and online as we discover nuggets of information that others have missed and post that information online. the tools we plan to use are n8n, obsidian, qdrant, docling. if you are interested in participating dm and tell me about your relevant experience and why you are interested. thx

in 2026 either you own the tech stack and the hardware on which you are hosting your AI automation or you are exploited for data, for knowledge and gated. Are you not smart enough to understand that in 2026 your data and your actions are the only value left. each person's actions and knowledge is converted into a product aka GPP (Gross Personal Product not Gross Domestic Product)

curious to learn what people think. tell me what SAAS, paid API AI subscription is not worth the money in 2026 and tell me why.

Hey Avengers, We had a discussion in the AI Avengers Lab this morning about the open source "Clawdbot" project. The question came up: "Cool tech, but how does this actually help a business?" Here is my take on it. This is not a tool. This is infrastructure. This is v0.1 of a widely democratized "Jarvis." Right now, when an employee leaves your agency, they walk out with: 1. Context. 2. Relationships. 3. Institutional memory. Your business effectively gets a lobotomy every time someone quits. Reframing this project: The AI is the Employee. When you run this locally (Sovereign AI): - Zero knowledge leaks. - Zero "memory loss" when staff changes. - The work stays with the AI, forever. The craziest part? YOU OWN THE IP. You can rebrand it, modify it, and sell it as your own SaaS or internal tool. Security warning: The "Prompt Injection" risk is real. This exposes your system to the web. Do not install this unless you understand the risks. But if you are ready to build, I am researching this deeply. I’ve forked the repo to create my own version: "Jarvis OS" Grab the repo here: https://github.com/manojsaharan01/jarvis-os Set this up for $0 using the cloud credits we all have access to: - Free VPS (AWS $200 credit) - Google Cloud API ($300 credit) - Azure OpenAI + GPT-4 ($1,000+ credit) - Telegram integration (text your AI from anywhere) That is $1,500+ in free credits for an AI assistant that never sleeps. This isn't just a toy. Imagine giving everyone on your team their own Clawdbot to handle research, coding, and basic tasks. That is the leverage play here. Links detailed below: watch Mani’s breakdown of the original setup here: https://youtu.be/kNZbpCtBITo ( Setup Guide _Google Doc ): https://docs.google.com/document/d/14NPo_zxeD4oi5Y6QRKOvDAPVDPwBkxUUTe_uNNsoab8/edit?usp=sharing

ClawdBot exploded overnight. 923 gateways exposed to the internet. Zero authentication. Full shell access. The crazy part? This isn't a bug. It's the default configuration. I woke up to my timeline flooded with screenshots: "Cleared my inbox while I slept!" "Rebuilt my entire website from my phone!" "Arranged next week's schedule autonomously!" Everyone celebrating the AI revolution. No one talking about the security nightmare. Here's what security experts found: 923 ClawdBot gateways directly accessible from the public internet. No password. No verification. Complete system control available to anyone who finds them. Not a rare vulnerability. Not a configuration error. The default behavior. When I saw this, I had one thought: This is how disasters start. Not with malicious intent. With excitement that blinds us to risk. If you installed ClawdBot this week, you need to read what comes next. Because what I'm about to share over the next few weeks could save your AI Agent. Stay tuned !