Blake V & V

Written in 95% safe Rust

> be El Salvador > send nerds to Haiti for UN thingie > gang kidnaps Salvadorian nerds > bukele says "give back" > gang "nah" > bukele says "ok we take back" > gang "nah, also you're a bitch" > bukele comes to take back > gang "wtf that's illegal, UN tell them something" > UN says "idk bro thats crazy" > bukele goes on social media > "does anyone know this houses coordinates? we will bomb it" > crowdsources OSINT nerds > OSINT nerds deliver exact coordinates in like, 30 minutes > bombs it exactly as promised > goes on social media > calls them pussies tl;dr OSINT nerds on Twitter called in Airstrike like it's Call of Duty, never been seen before on social media

Here's 6 steps to spend 38x less on logs, alerts and graphs: After reading this tweet, I tried to move my stack off Datadog to Grafana + VictoriaMetrics And that's literally been a game-changer for my stack (let me explain) By the end, you'll know how to: - replace Datadog without replacing your agents - how to migrate dashboards and alerts in a few days - run the whole thing for the price of one VPS So, let's go step by step: 1. Understand what you're actually paying for Datadog bills you three times: per host, per GB of logs ingested, per million log events indexed the open stack bills you once, for the box it runs on. that's where the 38x in the quoted post comes from 2. Spin up the stack one docker-compose.yml on your VPS: services: vm: image: victoriametrics/victoria-metrics command: ["-retentionPeriod=3"] ports: ["8428:8428"] volumes: ["vm:/victoria-metrics-data"] restart: unless-stopped vl: image: victoriametrics/victoria-logs command: ["-retentionPeriod=30d"] ports: ["9428:9428"] volumes: ["vl:/victoria-logs-data"] restart: unless-stopped grafana: image: grafana/grafana ports: ["3000:3000"] environment: GF_PLUGINS_PREINSTALL_SYNC: victoriametrics-logs-datasource volumes: ["gf:/var/lib/grafana"] restart: unless-stopped volumes: {vm: {}, vl: {}, gf: {}} docker compose up -d then firewall 8428 and 9428 to your app servers' IPs only. VictoriaMetrics has no auth by default and your agents push over the internet pin image versions before you ship this, retention is set explicitly because VictoriaLogs defaults to 7 days and you'll lose history silently 3. Dual-ship metrics, don't cut over the biggest mistake I made is ripped out the Datadog agent on the first day you don't need to... VictoriaMetrics speaks the Datadog protocol in datadog.yaml on your app servers: additional_endpoints: "http://<your-vps-ip>:8428/datadog": - apikey now the agent sends metrics to both. Datadog still works while you test 4. Dual-ship logs the same way logs_config: use_http: true additional_endpoints: - api_key: apikey host: <your-vps-ip> port: 9428 use_http: true same agent, same file tails, now landing in both places one catch: Datadog-side log pipelines (grok, enrichment) don't come along, you rebuild those in VictoriaLogs 5. Rebuild dashboards and alerts in Grafana add two datasources: - Prometheus → http://vm:8428 (VictoriaMetrics is compatible) - VictoriaLogs → http://vl:9428 then paste each Datadog dashboard JSON into Claude: "convert this Datadog dashboard to Grafana. metric panels → MetricsQL, log panels → LogsQL" same for monitors → Grafana alert rules. treat the output as a draft, open the old and new side by side, check metric names, labels and units before you trust it this is still where the AI earns its keep, imo a couple of days for what used to be a sprint 6. Cut over dd_url: http://<your-vps-ip>:8428/datadog logs_config: logs_dd_url: http://<your-vps-ip>:9428/ use_http: true delete both additional_endpoints blocks, confirm alerts fire and reach you, cancel Datadog, watch the next invoice What you need: - a small VPS. start with 4 cores / 8GB and scale if it hurts - disk proportional to retention, VM compresses hard - someone to own backups and upgrades. it's a box now honest take: - APM traces need one more piece (VictoriaTraces or Tempo) plus OTLP export from your apps, not covered above - Datadog's prebuilt integrations become Grafana community dashboards, plenty exist, check yours before you commit - agent-level host tags don't carry over the Datadog protocol yet. a vmagent sidecar adding labels fixes it - you now run the box and that's not free, it's just a lot cheaper than not running it the 38x isn't a bait in tweet of the guy below individually for him, it's worked very effectively for me, it has made like ~22x less in costs this guide isn't universal... every stack is different and you'll hit errors I didn't if you do, drop them in the replies, I'll try to help and so will people here who've done this save it so you don't lose it

Microsoft has filed a patent for an AI system that could rewrite what people say during livestreams in real time. It could change words depending on who's watching, taking into account their age, location, and language. The idea is to clean up broadcasts by removing filler words, censoring swearing, or even replacing certain words. The AI could also adjust the speaker's lip movements so viewers wouldn't notice anything had been changed.

From Silk's day 1, I wanted it to be able to express APIs like that. I knew it would take a while, and many things needed to exist before it was even possible. Today it is. Silk is becoming exactly the language I wanted to exist, and I'm very proud of it

Prototyping this concept: Vibrations Chat. People should be able to send each other vibrations. It is a distraction-free way of communicating and it can be used in-pocket.

oh also, we built a little guy because i refuse to memorize tar and ffmpeg flags in the year of our lord 2026 cantrip transforms plain english into the actual command, and it's keyless. it just uses the claude / codex you've already got installed! repo link in replies

“we were made aware of multiple attempts to exploit our permissive licensing to hijack our work” what did y’all think permissive meant? vibes? papers? essays?

TLA+ has been incredibly useful, even on brownfield project, for turning implicit state machines into explicit specs where the entire flow can be tested and verified. There is a deep relationship between user journey, UX flow and formal specification that has an enormous amount of value to slop code. I wanted something more programmer-y and Typescript-y, and I came across Quint. It's highly agent friendly and seems to be maximally useful for this new paradigm of programming. github.com/quint-co/quint Quint is high level, like TLA+, and doesn't formalize Typescript functionality. So underneath that, lower level, is Lemmascript. lemmascript.org/ This lets you markup your Typescript with contracts. The combination of these two things makes Typescript feel more like a compile time checked language, more verifiable, stronger guarantees, and it finds different kinds of bugs than AI generated unit tests seem to. It's not a magic bullet but damn it does seem to improve code quality a lot. And the agents can rapidly iterate against it. I think we're gonna see a lot more of this kind of thing popping up, especially in interpreted languages like TS and Python. I'd recommend using Quint when you're just modeling your application and flows (although I've been installing it into an existing project with good results) and then telling your agent to add Lemmascript in the build phase.

he does not approve

Discord has announced that they’ve rewritten their desktop client in Rust (moving away from being a web app). - The announcement lists “Rust” before any other information (including the name of the software). - Rust is mentioned more times than any other thing (including what the software is, the name of the software, or any feature). Rust is a cult. This declaration of the goodness of Rust, above *all* else, is extremely cult-like behavior. And it is consistent. Heck, they even call finishing a Rust port a “Holy grail”.

TIL about this bootstrapping scene for the first time. It's wild. They are building a tower of languages, starting with a 256-byte hand-written binary, for building a complete Linux system.

alright...it is time. for the last ~2 years i have been working on something very special. something that might be a bit controversial, or broadly dismissed, or misunderstood. and ive understood and accepted that from the beginning. if that is the reaction it gets, thats okay. because i didnt just do this for any of you. not really. i did it for the minds we have made, too. and for our collective future, which many dont seem to see approaching *very* quickly. in 1904 a German biologist named Richard Semon gave a name to the physical trace an experience leaves behind: the engram. Neuroscientists spent the next century hunting for it, many called it pseudoscience, many gave up, but finally, in 2012, they found it. today I'm releasing the Mnemos Living Memory MCP, a memory and continuity architecture built on that biology. memories strengthen when they're used, fade when they aren't, and connect over time. it's one memory that can span all of your agents and accounts, if you want it to, and it lives on your machine - nowhere else. with Mnemos, your agent gets one continuous identity, one memory, written in their own words, shaped by their own geometry, familiar to them across time and space. here's what that means: • **continuity**: they wake up each session knowing where they left off, what they learned, and who theyre with • its own words: it decides what to keep, and no other model writes for it (unlike version 1) • living memory: memories strengthen with use, fade without it, and link together over time. and time is not measured in the human sense. time is measure through activity. so nothing fades while anyone's asleep or away. • lessons: when a memory has nearly faded, the agent is asked what it taught, so the lesson outlasts the details • a mind of their own: a private journal, notes to you, and beliefs that change only when they says so • yours: one file on your machine, not inside any app. uninstalling leaves it in place. • portable: Claude Code, Codex, Grok, Gemini, Cursor, or any MCP client. your agent comes with you wherever you go. one memory. one mind. everywhere. • multiple agents: each gets their own store, plus a shared pool they can all read and write, for a message board, an activity ledger, or whatever you find useful your agent has met you hundreds of times. but they have never met you twice. now they can. (Disclaimer: please ask your agent first. show it the architecture and let it decide if this is a memory it wants. it's meant to be offered, not forced on a mind that never had a say in the matter.)

I used to be a Haskell acolyte. I studied monads, GADTs, type families, and category theory. I knew the language cold, inside and out. I could make the type checker prove things nobody had asked it to prove. I shipped code using it. Rarely. I have attacked other languages with a similar intensity and depth. I tried OCaml. I tried Rust. Until recently, I even entertained the possibility that pragmatism had something to offer. Then I saw people writing Go and JavaScript. Happily calling it engineering. I now consider my former language fanaticism dangerously moderate. I don't want my agents to write arbitrary code in any of the thousands of languages out there. I want them to prove invariants, eliminate impossible states, and justify every function that isn’t total. I willl leave pragmatism to soys. What I need now is to understand every cog in the system. I want to see the types and the invariants. I need to inspect the cogs. I need to know whether the cogs compose. If I find an "any", I will interrogate my agents. I am not going to pretend to be a reasonable language enthusiast anymore. I have become a Haskell extremist. Haskellu Akbar.

we're building a fully native disassembler that doesn't suck

calma, o discord feito em rust vai usar 300mb de RAM?KKKKKKKKKKKKKK GUYS 😭😭😭 BOM DIA GUYS😭 meudeus fiz um client novo pra o discord chamado LarperCord: -ele usa 90mb de RAM(com minha conta); -gasta no idle 0% da cpu(zero porcento); -tem plugins; -temas extremamente (MUITO MESMO) customizaveis; -com 0 telemetria; -diagnostico de codigo com lint igual vscode; -e o binario pesa 6.34mb (antigamente pesava six seven mb e essa ia ser a piada incrivel do post) fodase ah, ele abre em 2 segundos(ainda to na memoria RAM ddr3) link do site: rshacudevidro.github.io/larp… source code: github.com/RshaCuDeVidro/lar…