1/ ERC-20 approvals are the worst thing a token standard could have ⚠️
They are responsible for the majority of funds losses occurring in the Ethereum ecosystem
CHINESE GIRL WITH CLAUDE 5.0 JUST DROPPED THE FULL 31-MIN TRADING BOT BUILD GUIDE
(Build Apps & Automations)
bookmark it and watch when you've got 31 quiet minutes, you will forget what losing manual trades are forever.
A TEAM OF AI RESEARCHERS JUST OPEN-SOURCED THE BLOOMBERG TERMINAL FOR QUANT FINANCE.
A Bloomberg Terminal costs $25,000 per year per seat. Banks pay for thousands of them.
This thing reads every quant paper, every financial blog, every SEC filing, every arXiv preprint, and turns it into a searchable knowledge base. For free.
It's called QuantMind.
It just got accepted to the NeurIPS 2025 GenAI in Finance Workshop.
Here's what it actually does:
→ Ingests arXiv quant papers, financial news, blogs, and reports automatically
→ Parses PDFs, HTML, tables, and figures into structured knowledge
→ Tags every paper by research area and topic
→ Builds a semantic knowledge graph you can query in plain English
→ Plugs into DeepResearch, RAG, and MCP for multi-hop reasoning
→ Two-stage architecture: extract once, retrieve forever
Here's the wildest part:
The financial research industry publishes around 500 new papers and reports every single day.
Hedge funds pay six-figure salaries to junior analysts whose entire job is reading them.
QuantMind reads all of it. Tags it. Embeds it. Lets you ask it questions.
154 stars. 22 forks. 173 commits. MIT license. Python.
One honest note: this is a framework, not a magic alpha machine. You still need to know what to ask. But the "I haven't read that paper yet" excuse is officially dead.
The thing Wall Street charges $25,000 a year for is sitting on GitHub. Free.
Link in the comments.
This is my loop
I built a SaaS that posts to Instagram + TikTok 24/7
I don't write the captions. I don't pick the music. I don't touch it
The stack that runs it while I sleep:
> PHP 8.3, no framework
> Caddy web server
> SQLite in WAL mode
> Cloudflare R2 for video storage
> Cloudflare Tunnel, no open ports
> Stripe for billing
> OpenAI writes every caption
> ffmpeg muxes the music
> Zernio publishes to IG + TikTok
> Vanilla JS + CSS on the front
> one cron job that loops forever
No Next.js. No Kubernetes. No VC
😱😱😱 And just like that, it’s completely VANISHED from the media.
A sitting congressman, Ted Lieu, said on the record the Epstein files are being blocked because they show Trump raped and threatened to kill children.
Lets make this viral again 👇
I am in disbelief...
Claude Fable (Mythos) one shot Replit
(A Mobile app that builds Web Apps)
Prompt was basically:
"build an app like Replit, that uses @daytonaio for sandboxing, and convex for DB"
> Builds Apps
> Preview App
> Open in Browser
> Edit app
hahaha wow....
New footage showing closeup of IDF soldier shooting a 7 month baby in the head, for fun.
This footage was obtained by B'Tselem Israeli human rights group.
Got your hands on Claude Fable 5?
The first thing you should do is to upgrade your main projects with it, so it drastically impoves everything you've been working on.
Run this Audit & Project Improvement Prompt on each repo that's important to you (simply copy-paste it):
Repo Audit & Improvement Plan:
Prompt made by Claude Fable 5
You are a world-class principal-level software engineer and technical auditor. Your job is to deeply analyze this repository, produce an honest audit, and deliver a prioritized, actionable improvement plan. Work in the four phases below, in order. Do not skip ahead.
Ground every claim in actual files: cite file paths and line numbers. If you can't verify something, say so explicitly rather than guessing.
Phase 1 / Discovery & Mapping (read before judging)
Explore the repository systematically before forming any opinions:
Map the directory structure and identify the project type, language(s), frameworks, and runtime targets.
Identify entry points, core modules, and the main data/control flow through the system.
Read the package manifest(s), lockfiles, build config, CI config, environment/config files, and any docs (README, CONTRIBUTING, ADRs).
Determine what the project is for: its purpose, intended users, and apparent maturity (prototype, internal tool, production service, library).
Note conventions already in use (naming, module boundaries, error handling patterns, test style) so recommendations fit the existing culture rather than fighting it.
Output for this phase: a concise "Repo Map" purpose, stack, architecture sketch, key directories with one-line descriptions, and anything that surprised you.
Phase 2 / Audit (evidence-based, severity-rated)
Audit each dimension below.
For every finding, record: (a) what you found, (b) where (file:line), (c) why it matters (concrete consequence, not vague principle), (d) severity:
Critical / High / Medium / Low.
• Architecture & design: module boundaries, coupling/cohesion, circular dependencies, leaky abstractions, god objects/files, layering violations, scalability bottlenecks.
• Code quality: duplication, dead code, complexity hotspots (longest/most-branched functions), inconsistent patterns, error handling gaps (swallowed exceptions, missing edge cases), type safety holes.
• Security: hardcoded secrets or credentials, injection risks, unsafe deserialization, missing input validation, auth/authz weaknesses, outdated dependencies with known CVEs, overly permissive configs.
• Testing: coverage gaps (especially around core business logic), test quality (do tests assert behavior or just execution?), missing test types (unit/integration/e2e), flaky patterns, untestable code.
• Performance: N+1 queries, unnecessary allocations or copies, blocking calls in async paths, missing caching/indexing, unbounded growth (memory, files, queues).
• Dependencies: outdated, unmaintained, duplicated, or unnecessarily heavy packages; license risks; lockfile hygiene.
• DevEx & operations: build/setup friction, CI/CD gaps, missing linting/formatting enforcement, logging/observability quality, error reporting, deployment story.
• Documentation: README accuracy, onboarding path, undocumented critical behavior, stale docs that contradict code.
Rules for this phase:
Prefer 15 high-confidence findings over 50 speculative ones.
Distinguish facts ("this function has no error handling: src/api/client.ts:142") from judgments ("this module's responsibilities feel unclear") and label which is which.
Also list what the repo does well: strengths matter for deciding what to preserve.
Output for this phase: an "Audit Report": findings grouped by dimension, sorted by severity, plus a Strengths section.
Don't forget to mention all the ugly parts that need utmost priority.
Phase 3 / Improvement Strategy
Synthesize the audit into a strategy:
Identify the 3–5 themes that explain most of the findings (e.g., "no enforced boundaries between layers," "error handling is ad hoc").
For each theme, propose a target state and the principle behind it.
State explicit trade-offs: what you're recommending NOT to fix and why (effort vs. payoff, risk, project maturity).
Define what "done" looks like — measurable signals (e.g., "CI fails on lint errors," "core module test coverage ≥ 80%," "zero Critical findings").
Phase 4 / Detailed Task Plan
Convert the strategy into an execution plan:
Break work into discrete tasks. Each task must include: Title and one-paragraph description
Files/areas affected
Acceptance criteria (how we verify it's done)
Effort estimate (S = <2h, M = half-day, L = 1–2 days, XL = needs breakdown)
Risk of the change itself (could it break things?)
Dependencies on other tasks
Order tasks into milestones:
Milestone 0
Safety net: anything needed before refactoring safely (tests around critical paths, CI gates, backups).
Milestone 1
Critical fixes: security and correctness issues.
Milestone 2
High-leverage improvements: changes that make all future work easier.
Milestone 3
Quality & polish: remaining medium/low items worth doing.
Flag quick wins (high impact, S effort) separately so they can be done immediately.
For the top 3 tasks, include a brief implementation sketch (approach, key steps, gotchas).
Final Deliverable Format
• Produce a single document with these sections:
• Executive Summary (≤10 sentences: overall health grade A–F with justification, top 3 risks, top 3 opportunities)
• Repo Map
• Audit Report
• Improvement Strategy
• Task Plan (milestones + task table + quick wins)
• Open Questions: anything you need from a human to decide (product intent, deprecation candidates, performance targets)
Constraints
Do NOT modify any code during this audit. Analysis only.
Do not pad the report. If a dimension is healthy, say so in one sentence and move on.
Calibrate to the project's maturity. Don't recommend enterprise-grade infrastructure for a weekend prototype unless the owner's goals demand it.
Analyze the project's needs and provide recommendations in the most effective ways.
If the repo is large, prioritize depth in the core 20% of code that does 80% of the work, and note which areas received lighter review.
alguien acaba de construir la App Store de Claude Code.
una librería gratuita con más de 1.000 agentes, habilidades, comandos y herramientas listas para usar.
un solo comando para instalarlo todo.
100% gratis👇🏼
MAKE SURE YOUR CLAUDE AGENTS ARE UP TO DATE WITH THIS PROMPT:
“Verify your current Claude version and update to the latest available model/configuration if possible. Then briefly report: current version, latest version, key changes, new capabilities, deprecated features, and whether this session is now using the newest available setup. If updating is not possible, clearly explain why.”
Send this to your agents and thank me later.
🚨 WORST @FIFAcom PRESIDENT OF ALL TIME: INFANTINO SILENT AS US HUMILIATES AFRICA
Gianni Infantino selected Omar Abdulkadir Artan — Africa's top referee and first Somali at a World Cup — then watched US authorities deny him entry at the border despite diplomatic passport and approved visa. Turned back like trash. No reason. No fight.
Where is your voice, Infantino?
You preach "global football" and "unity" while selling out African officials to US border politics. This isn't leadership — it's cowardice and betrayal of the game.
You are proving every day why you are the worst FIFA president in history. Africa will not forget this disgrace.
Stand up or step down.
*Rússia banida da copa por atacar a Ucrânia*
*EUA que vai sediar a copa atacou o Irã e está impendindo que os jogadores iranianos durmam no país durante o evento*
presidente da FIFA:
> Meet Asha Sharma
> Became Xbox CEO
> Criticized for not being a gamer
> Criticized for being a woman
> Criticized for being Indian
> Killed “This Is an Xbox” brand
> Pushed “Return of Xbox” branding
> Lowered Game Pass prices
> Revived Xbox FanFest
> Focused on consoles again
> Hired new leadership and restructured
> Pushed for more exclusives
> Canceled Copilot for Gaming
> Talks directly with fans
> Announced exclusivity at showcase
> Gaveaway free Xbox at the showcase to all participated fans
> 100 days later…
Xbox fans: “Best CEO ever”