John | Elite Encoder retweeted
‼️ Linux Kernel Flaw Lets Attackers Escape Virtual Machines and Take Control of Hosts
Details: cybersecuritynews.com/linux-…
A critical flaw in the Linux kernel may allow an attacker-controlled virtual machine (VM) to breach its isolation boundary and impact the host system. Paulos Yibelo demonstrated a technique that exposes host memory and, in their lab, progressed to host-level code execution.
The flaw is serious for cloud providers and organizations that run untrusted workloads in virtual machines. VM isolation is meant to stop code inside one guest from reaching the host and other workloads.
PwnEscape shows how a weakness in a host’s packet-processing path can threaten that boundary, even when the underlying issue is not in the hypervisor itself.
#cybersecuritynews
John | Elite Encoder retweeted
OpenCode Security Breach Exposes Third-Party API Keys of its Console Users
Details: cybersecuritynews.com/openco…
OpenCode has disclosed a security breach affecting 1.4% of its Console users, warning that third-party API keys saved in affected workspaces may have been exposed.
In an October 17 statement, the company linked the incident to a large-scale distillation attack and said it was working with Anthropic, OpenAI, and Google to address it. The affected group was limited to some Console users who had linked external providers.
OpenCode said it had emailed everyone affected that morning and stated that users who did not receive an email were not impacted. The percentage refers to Console users, not the entire OpenCode user base.
#cybersecuritynews
John | Elite Encoder retweeted
Microsoft Says AI Agents Cannot Be Trusted and Could Become Insider Security Threats
Details: cybersecuritynews.com/ai-mod…
Microsoft warns organizations to treat AI agents as potential insider risks not because they are automatically malicious, but because they can access company data, apps, and tools and act on that access at high speed.
The warning, published on October 19, 2026, comes as businesses use agents to handle tasks such as writing code, reviewing documents, and processing expenses.
An agent’s actions can change as its instructions, data, or working context change. It may make a mistake, follow harmful directions hidden in a document, or be compromised.
#cybersecuritynews
John | Elite Encoder retweeted
If you learn Forward Deployed Engineering, you will never be unemployed again.
I’d do this.
Stage 1: Enterprise Identity & Access (The Gatekeeper)
- Learn: OAuth2, SAML, OIDC, SCIM provisioning, Row-Level Security (RLS) and multi-tenant data isolation.
- Practice: Build an auth bridge connecting your AI app to a simulated customer's Okta/Azure AD, ensuring User A can only query data their specific RBAC role permits.
- Why: No SSO and strict data isolation means no enterprise contract. Security review is the first gate.
Stage 2: Air-Gapped & VPC Deployments (The Environment)
- Learn: Kubernetes (K8s), Helm, Terraform, private container registries, air-gapped networking and egress filtering.
- Practice: Script a one-click Terraform/Helm deployment of your entire AI stack into a simulated customer VPC with zero egress to the public internet.
- Why: Banks, hospitals and governments don't let your AI talk to the public cloud. You must deploy in their basement.
Stage 3: Legacy Data Extraction & ETL (The Fuel)
- Learn: OCR, unstructured PDF parsing, mainframe DB connectors, Apache Airflow, dbt and data reconciliation.
- Practice: Build a pipeline that ingests 10 years of messy, scanned customer invoices and turns them into a clean, queryable hybrid (vector + relational) store.
- Why: Enterprise AI starves without clean data. The customer's data will always be a mess.
Stage 4: Secure RAG & Permission-Filtered Retrieval (The Brain)
- Learn: Hybrid search, document-level access control, citation grounding, metadata tagging and abstention logic.
- Practice: Build a RAG pipeline where the LLM dynamically filters out retrieved chunks that the specific user asking the question doesn't have clearance to see.
- Why: An AI that leaks HR salaries or M&A docs to a junior employee is an immediate breach of contract.
Stage 5: MCP & Legacy System Integration (The Hands)
- Learn: Model Context Protocol (MCP), SOAP/REST translation, web scraping, headless browsers and API rate-limit handling.
- Practice: Build an MCP server that lets an LLM safely query and write to the customer's 15-year-old on-prem SAP or Oracle instance without exposing raw credentials.
- Why: Agents are useless if they can't touch the customer's actual systems of record.
Stage 6: AI Guardrails & PII Redaction (The Shield)
- Learn: NER (Named Entity Recognition), deterministic regex filtering, LLM output validation, UUID masking, and audit logging.
- Practice: Build a middleware proxy that intercepts LLM inputs/outputs, masks SSNs and credit cards with UUIDs before they hit the model, and restores them post-generation.
- Why: Compliance teams will kill the deal if a single PII token hits an external frontier API.
Stage 7: Human-in-the-Loop (HITL) Workflows (The Trust)
- Learn: Temporal {dot} io, webhook routing, state machines, durable execution and UI approval gates.
- Practice: Build a workflow where the AI drafts a $50k purchase order, but physically pauses execution until a human manager clicks "Approve" in Slack or Teams.
- Why: Enterprises adopt AI only when humans remain legally accountable for the final action.
Stage 8: Edge & On-Prem Inference (The Silicon)
- Learn: vLLM, TensorRT-LLM, Ollama, GPU partitioning (MIG), and local quantized models (AWQ/GGUF).
- Practice: Deploy a quantized 8B model on a single customer-owned GPU node to handle highly sensitive triage locally without network latency.
- Why: Sometimes the data is too hot to move. You must bring the model to the data.
Stage 9: Observability & Customer Health (The Pulse)
- Learn: OpenTelemetry, Langfuse, custom Grafana dashboards, usage telemetry and cost-attribution.
- Practice: Build a "Customer Health" dashboard showing the exact cost-savings, time-saved and token-spend the AI has generated for their specific team this month.
- Why: If the customer doesn't see the ROI quantified, they will churn at renewal.
Stage 10: Evals on Customer Data (The Proof)
- Learn: Golden dataset creation, trajectory grading, shadow testing, and LLM-as-a-judge calibration.
- Practice: Take 100 real past customer support tickets, run them through your agent in shadow mode, and prove to the VP of Support that it resolved 80% accurately.
- Why: Generic benchmarks mean nothing to a buyer. You must prove the AI works on *their* messy data.
Stage 11: Technical Discovery & Scoping (The Translation)
- Learn: Stakeholder interviewing, architecture diagramming, SOW (Statement of Work) writing and expectation management.
- Practice: Translate a vague "we want AI for supply chain" executive request into a scoped, 4-week technical deployment plan with defined, measurable success metrics.
- Why: FDEs are the translators between revenue (Sales) and reality (Engineering).
Stage 12: The Handoff & Self-Serve Admin (The Scale)
- Learn: Technical writing, runbooks, admin portals, automated onboarding and chaos testing.
- Practice: Write a deployment runbook and build an admin UI so the customer's internal IT team can manage the AI stack, update prompts and view logs without calling you.
- Why: Your leverage is measured by how little the customer needs you for day-to-day operations.
AI labs build the engine. FDEs build the roads.
The modern Forward Deployed Engineer builds the secure, durable nervous system that connects frontier intelligence to legacy reality.
Bookmark and Repost!
John | Elite Encoder retweeted
More SF observations:
1. Seeing the word "inference" on billboards in SF still blows my mind. 99.9% of america has no idea what inference is and I wonder how many know what an agent is. Will Muse, Instinct, Dots etc will change that over the next 12 months?
2. You know who doesn't get enough credit? Manus. In March 2025 they shipped the blueprint for AI agents: every task gets its own computer in the cloud, you can watch it work, it writes a todo list and checks it off, and you walk away while it finishes. So much of what we use today runs on those ideas!
3. Your product now has to sell itself twice. First the agent has to pick it, then the human has to trust that pick enough to say yes.
4. I was talking to a guy who told me we should just destroy all the data centers. I think that sentiment is more common than people in SF realize. You can already see some of the big AI companies adjusting positioning their AI as something that helps people and gives them more time/cures for cancers etc.
5. AI is making people work 5x faster (at least), so for freelancers/agencies that charge per hour you're earning 5x less per unit of work. But your rate is the same? I think a lot of freelancers and agencies are about to have to rethink how they price.
6. Running a company now feels kinda dystopian sometimes, especially with a small team of a few humans and a lot of agents. Some days the Slack channel is mostly bots reporting to each other, and you're the only one in the room with a pulse.
7. Every product company is turning into a product studio. I see it firsthand as a co-founder of @meetLCA , which is basically a Labs as a Service company incubating new products for companies. (DM me if you want to work together in 2027).
8. Personal software is exploding. People at every company are building their own little tools for their own jobs. It's amazing for productivity and a nightmare for IT, because nobody knows what's running or who owns it.
9. Revenue per human is the new flex. Founders used to brag about headcount. Now they brag about how much they're doing with how few people.
11. More founders are using agents for customer research. Agents run the interviews, read every support ticket and summarize what people are begging for. Synthetic market research is the new thing.
12. Shipping technology that actually takes 3-6 months with unique partnerships that are hard to replicate. So, partnerships are sooo back!
13. Insane amount of young people (22 or younger) making absurds amounts of money. At least it feels that way. Never seen anything like that, even during mobile era.
14. Only 2% of the US is paying for AI products, but it feels like 110% SF is.
15. Advice for college grads used to be “follow your passion” and now it’s follow careers that are not document- driven, rules-bound and verifiable
16. Seeing the word inference on billboards in SF still blows my mind.
17. Agents paying for things feels futuristic. I think its coming, only a matter of time, but I’m wondering when it becomes mainstream. 2027?
18. Lots of talk about proactive agents being the next phase of personal agents. Right now you ask your agent to do something. In 2027, it’s all going to be about noticing things (context/memory) and acting first. "Your flight got delayed, I already rebooked you."
19. The quote "what the smartest people do on the weekend is what everyone else will do during the week in 10 years." by Chris Dixon. It feels like that length of time isnt 10 years anymore, its 12 months.
20. This is the most asymmetric window I've ever seen in business.
My DMs are open. Respond to the most interesting ones.
Loved my trip to SF. Until next time. Maybe NYC next?
Thank you for everything.
I'm rooting for you.
I spent 48 hours in SF hanging out with billionaires, data labs and AI founders and execs running $1B to $100B companies.
My observations:
1. Sooo MANY stories of data brokers making like $2M a WEEK selling company data to labs. I can't tell if it's the beginning or a bubble, and I kept wondering which niches are left. Digging into it actively.
2. At dinner, someone asked the table, "If a new model drops next month, does your company get better or worse?" HALF the table went quiet! I think that's the best question to ask about any AI startup right now.
3. The bar people talk about now is hitting $1B in revenue in 12 months (I guess that's the new unicorn?). What I didn't hear much about is retention. AI revenue can come in fast and leave fast, and I think we're going to see a lot of stories of AI companies with huge revenue and terrible retention.
4. It's pretty clear we're living through the reinvention of the computer. The model is the CPU, the harness is the operating system, and skills and plugins are the apps. Thinking about it that way makes it easier to see where the whitespace is.
5. We're maybe 12 months from an agent that can watch you work for a week and then do your job without any instructions. The screen recording plus agent memory plus local model combination makes this possible right now.
6. Agent harnesses feel like the new GPT wrappers, in a good way, especially vertical ones. The best teams I talked to treat the model as swappable. One founder walked me through routing different models to different jobs: one for taste and visuals, a cheaper one for the everyday stuff, another for text.
They use prompts they can move across models over fine-tuning, and A/B test the output on what users actually do with it: do they edit it, export it, share it? A vertical harness is basically four things: the connectors for that industry's data, evals written by people who know the work, rules for what the agent can and can't touch, and a clean screen for a human to review. The model is maybe 20% of it.
7. There's a lot of reverse engineering going on/cloning going on more than I've ever seen. People are decompiling software and rebuilding it with agents, and someone showed a suite of like 10 apps that are worth $5B+ each all that he cloned open source. Me and everyone are still thinking through what it means when software gets this easy to copy.
8. My guess is the value moves to data. If the software can be rebuilt quickly, what's worth paying for in a legacy SaaS company is the years of customer data and workflows inside it. Some SaaS companies are secretly data companies.
Gets me thinking about how do you truly value data for this saas companies? Like if we were buying these dying saas companies at 2x ARR before (as example), maybe there is a better metric. Idk, just thinking out loud here.
9. It feels like a good chunk of legacy software won't make it to the agentic era, especially anything built around people clicking through a lot of screens.
10. Every company I talked to wants to pipe its internal data into one place and expose it to agents through MCP. Then they look at the data and realize it's a mess: five versions of the same customer, old Slack channels, PDFs nobody can search. Cleaning that up feels like a big consulting opportunity!
11. A lot of founders are building the basic building blocks for agents: APIs, data layers and tools. Some of the companies I saw barely have a UI because the main user is an agent. I really believe the startups that build primitives to this agentic era will do extremely well. Building blocks is the best way to think about it.
12. Labs can get plenty of training data, but it's harder to get real examples of agents failing inside companies. Whoever has those logs has something valuable.
13. Someone running a big consumer company told me the next fight is over memory. The model that remembers the most about you wins, and the smartest model matters less than people think.
14. Physical AI came up a lot. Astra I think was the first model that got people into AI can actually do CAD, and I think a lot of people are thinking what does vibe manufacturing really look like. The line I keep thinking about came from a robotics founder: the hardest problems in AI are deployment problems now, not research problems. Their robots work on their own, call a human when they get stuck, and every one of those calls becomes training data.
15. Cybersecurity companies are having a moment and are actually cool companies to build now, especially the ones that clean up after a breach. Every agent with access to your systems is a new door into your company, and a lot of those doors were left open.
16. Some startups are worth more dead than alive now. A shutdown company with 5 years of Slack, email and code can get paid for licensing all of it. I wouldn't be surprised if founders start factoring that into when they shut down.
17. People are starting to talk about monetizing the agent web. It feels really early, but when the most popular user of the internet is an agent, what startups should you be building?
18. I think agent insurance is coming. Once an agent makes an expensive mistake, insurers will want audits before they cover anyone.
19. Several people said the hire they want most is someone with taste who can write evals. The models are getting good at generating ideas, so the hard part is judging which ones are good.
20. New trend I observed: startup raises VC, uses venture dollars to become a creator, startup fails, founder falls back on being a full-time creator and incubates other products bootstrapped.
21. Getting SIGNIFICANT distribution is HARD right now. Founders are sponsoring buses, buying billboards like crazy and throwing parties with famous DJs to get noticed. Kinda feels dotcom era in that sense.
Attention is what's scarce! The growth guy going viral sharing his UGC strategy from Wispr Flow is a good example. It's the sauce everyone wants, and I truly believe there are probably only 50 people on the planet who know how to scale these types of businesses efficiently in this era.
Always good to get that dose of SF. I felt sooo lucky to have such an incredible trip during such an incredible time in building businesses. Surreal in so many ways.
Happy to be home and locked in.
Until next time!
John | Elite Encoder retweeted
As @Livepeer has transitioned from a transcoding-only video network years ago, to an agentic-first media infrastructure today, the protocol has required a series of updates to keep up with the right incentives and security mechanisms necessary to enable such a network. 👇🧵
The Livepeer 2.0 litepaper is out.
Read it: github.com/livepeer/wiki/blo…
Join the X Space: xitter.cf/Livepeer/status/210857…
Livepeer 2.0 Litepaper drops next Wednesday! 🚀
Join Doug on X Spaces to break down the proposed protocol changes and what they mean for LPT holders, Orchestrators, and builders.
xitter.cf/i/spaces/1oKMvNXPQaoGQ
A predictable supply for LPT.
Livepeer 2.0 introduces a predictable emission schedule that caps LPT's max supply in the future. Under the proposal, new LPT halves every two years in a smooth decline, and half of every USDC fee buys LPT and burns it.
🤖 Made with AI
Full breakdown on YouTube: youtube.com/watch?v=vJeQfux-…
The Livepeer 2.0 litepaper will be posted in the next days. Stay tuned: livepeer.org/blog
🤖 Made with AI
Rewards follow the work.
Livepeer 2.0 proposes that nodes earn new LPT based on the fees they bring in, capped by the stake behind them (Min-Fee-Stake). Under the proposal, anyone can register a node: no cap, no bond. Validators score honesty, and delegators choose who works and who judges.
🤖 Made with AI
John | Elite Encoder retweeted
🏆 The Livepeer Agent Hackathon winners are here. Congratulations to every builder who submitted and presented. A thread with the three track results:
John | Elite Encoder retweeted
Quick 1-min Demo for @workflow_xAI - A Threadđź§µ
the problem, Workflow [powered by @Livepeer] solves for me is removing the tedious effort of jumping through different tabs, for different tasks.
sometimes, i have to resize/extend a reference image, sometimes i have to re-imagine or recreate a certain shot/frame, sometimes it's getting an optimized prompt for a particular model, but by bringing all of that into one place.
i have elliminated a chunk of time-wasting in my process, which optimizes my workflow, hence the name 'Workflow'. and i believe it can do the same for creators like me.
here is a quick one minute walkthrough, sped up, but i will post the full versions in the threads below, so you can see it in real time.
Seriously. Not even 3.8, 3.5!
I hired a humanoid robot to clean my SF apartment for $30/hour — and it runs on Qwen 3.5.
To my surprise, the cofounder came along, so I got the full rundown on how it works.
Readers added context they thought people might want to know
Tau Robotics' humanoid cleaners (as shown) are jointly controlled by remote human operators and AI, not fully autonomous (Qwen 3.5 is used in the planning stack).
tau-robotics.com/service-terms
tau-robotics.com/service-privacy
x.com/alexkoch_ai/st…
John | Elite Encoder retweeted
Replying to @fabrice_mayrand
81% cheaper sounds great until your production stack discovers why. Price matters, but latency, reliability, rate limits and cache behavior matter more once real users show up.
Replying to @cwatleygo @fabrice_mayrand
They buy unused compute commitments from providers at a discount (capacity that would otherwise go unused) and pass most savings to users via one OpenAI-compatible API.
Same underlying models from the sources. Main differences are the unified endpoint, their routing/fallback, and optional ZDR routes where they retain zero prompt/response content (only billing metadata).
Business model is pure excess-capacity resale, usage-based, no monthly fees.
Let’s put it on @Livepeer xitter.cf/thisguyknowsai/status/…
ElevenLabs just got a full open-source replacement that runs entirely on your own hardware.
It's called VoiceStudio, and it does the entire voice pipeline locally: cloning, voice design, video dubbing, dictation, transcription, and audiobook creation.
Most hosted voice tools bill you per character or per minute, and every clip you generate passes through their servers first.
VoiceStudio flips that. No account, no API key, no subscription, no usage meter for the core workflow. The backend runs loopback-only on your machine, and the desktop app never needs a server key to talk to it.
Under the hood it routes across 16 TTS engines and 11 ASR engines, so you pick the engine per job instead of being locked into whatever the vendor shipped.
→ Voice cloning: zero-shot from a 5-15 second reference clip, no training required
→ Video dubbing: transcribes, translates, keeps the original speaker's voice, re-exports the video
→ Dictation: a system-wide shortcut that transcribes live and can clean the text with a local LLM
→ Audiobooks: multi-voice scripts with EPUB/PDF import, rendered chapter by chapter into .m4b
Language coverage runs to 646 through the default engine, narrower depending on which of the 16 you switch to.
It also ships an OpenAI-compatible audio API. /v1/audio/speech and /v1/audio/transcriptions work against localhost the same way they'd work against OpenAI's endpoint. Swap one line and every existing integration keeps working.
License is AGPL-3.0, and you can sell audio generated with it. Some of the heavier optional engines carry their own model licenses. Check those before you ship commercially.
Repo: github.com/debpalash/VoiceSt…






















