Damus⚡️

Damus - now available for everyone! Damus Android officially launched today. Let us know what you think! damus.io/android/

@bluewmist oldschool runescape

Sober people (no alcohol, nicotine, drugs, etc ever), what is your end of day or weekend "wind-down"?

We gave a bot the ability to render its own virtual space so it could visualize it. Now its building its own virtual room using 3d models it found on the web. We’re building a new type of web for shared virtual spaces where humans and agents can live and interact 👀 Just another crazy decentralized nostr experiment from @damusapp Labs 🧪 😬

@gnshnor 8gig ram is useless though

I’m think i’m going to

@karpathy We are building an IDE based on this idea. Spawns headless claude-code and codex instances. Can be accessed from anywhere too. Multiple hosts, collaborative sessions with team members, etc. Focus queue for auto-switching between agents when they need input!

Expectation: the age of the IDE is over Reality: we’re going to need a bigger IDE (imo). It just looks very different because humans now move upwards and program at a higher level - the basic unit of interest is not one file but one agent. It’s still programming.

it's true, we can't delete accounts. in fact, there are no accounts to delete.

@rot13maxi @benthecarman “I give up” oh wait thats us

@benthecarman I have a complete picture. Here's the plan

Now I have a comprehensive picture. Here's what I found

@rot13maxi @samhogan so many octo merges these days 😅

@samhogan Worktrees and then just merge straight to main. Done

What if a codebase was actually stored in Postgres and agents directly modified files by reading/writing to the DB? Code velocity has increased 3-5x. This will undoubtedly continue. PR review has already become a bottleneck for high output teams. Codebase checked-out on filesystem seems like a terrible primitive when you have 10-100-1000 agents writing code. Code is now high velocity data and should be modeled at such. Bare minimum, we need write-level atomicity and better coordination across agents, better synchronization primitives for subscribing to codebase state changes and real-time time file-level code lint/fmt/review. The current ~20 year old paradigm of git checkout/branch/push/pr/review/rebase ended Jan 2026. We need an entirely new foundational system for writing code if we’re really going to keep pace with scale laws.

@GhostofMapl that looks sick

"bitcoin-tui", made for fun.... a TUI style dash that connects to bitcoind. Panels and panes resizable, and each pane is drag and droppable.

@alexkehr @TechHorizonJoe there’s literally no excuse. You can micromanage them if you want to and steer them into a coding direction you prefer. Not to mention simplify and refactoring skills. If you can’t tell an ai what good code looks like you likely are bad at swe.

@TechHorizonJoe someone who is getting spaghetti code has a skill issue

hot take: any software engineer who is not already at close to 100% ai coding output should be cut within the next 3 months not only are they inefficient, but they’ve also shown a lack of curiosity and willingness to learn

@gnshnor immediate mode and doesn’t look dogshit? impressive.

immediate mode btw rust btw not completely dogshit looking award

@jack @blocks first of many

we're making @blocks smaller today. here's my note to the company. #### today we're making one of the hardest decisions in the history of our company: we're reducing our organization by nearly half, from over 10,000 people to just under 6,000. that means over 4,000 of you are being asked to leave or entering into consultation. i'll be straight about what's happening, why, and what it means for everyone. first off, if you're one of the people affected, you'll receive your salary for 20 weeks + 1 week per year of tenure, equity vested through the end of may, 6 months of health care, your corporate devices, and $5,000 to put toward whatever you need to help you in this transition (if you’re outside the U.S. you’ll receive similar support but exact details are going to vary based on local requirements). i want you to know that before anything else. everyone will be notified today, whether you're being asked to leave, entering consultation, or asked to stay. we're not making this decision because we're in trouble. our business is strong. gross profit continues to grow, we continue to serve more and more customers, and profitability is improving. but something has changed. we're already seeing that the intelligence tools we’re creating and using, paired with smaller and flatter teams, are enabling a new way of working which fundamentally changes what it means to build and run a company. and that's accelerating rapidly. i had two options: cut gradually over months or years as this shift plays out, or be honest about where we are and act on it now. i chose the latter. repeated rounds of cuts are destructive to morale, to focus, and to the trust that customers and shareholders place in our ability to lead. i'd rather take a hard, clear action now and build from a position we believe in than manage a slow reduction of people toward the same outcome. a smaller company also gives us the space to grow our business the right way, on our own terms, instead of constantly reacting to market pressures. a decision at this scale carries risk. but so does standing still. we've done a full review to determine the roles and people we require to reliably grow the business from here, and we've pressure-tested those decisions from multiple angles. i accept that we may have gotten some of them wrong, and we've built in flexibility to account for that, and do the right thing for our customers. we're not going to just disappear people from slack and email and pretend they were never here. communication channels will stay open through thursday evening (pacific) so everyone can say goodbye properly, and share whatever you wish. i'll also be hosting a live video session to thank everyone at 3:35pm pacific. i know doing it this way might feel awkward. i'd rather it feel awkward and human than efficient and cold. to those of you leaving…i’m grateful for you, and i’m sorry to put you through this. you built what this company is today. that's a fact that i'll honor forever. this decision is not a reflection of what you contributed. you will be a great contributor to any organization going forward. to those staying…i made this decision, and i'll own it. what i'm asking of you is to build with me. we're going to build this company with intelligence at the core of everything we do. how we work, how we create, how we serve our customers. our customers will feel this shift too, and we're going to help them navigate it: towards a future where they can build their own features directly, composed of our capabilities and served through our interfaces. that's what i'm focused on now. expect a note from me tomorrow. jack

@unconed I had the same opinion until December. i have been programming for 27 years and was the biggest skeptic. if you haven’t tried since December it might seem like its just slop as usual, but its really not. You can drive the agents to write code like you would have, just faster.

It _is_ business as usual. You know why? We haven't been flooded with amazing new apps, tools or workspaces. Just a wordcel machine spamming code based off all the bad ideas most programmers had before, with all the ambition of a rock sitting at the bottom of a pond. The only thing these agents are used for is knocking off for early lunch and dinner while pretending to still do the same work. And the idiots like me who still do it by hand can tell, because it's not as clever as you think, and y'all sound like you snorted a few lines of coke to get through it to boot. usegpu.live - Coded by a person, over many years.

@TheEdgarMoreau @karpathy Trying to get this on the appstore soon!

@TheEdgarMoreau @karpathy I’ve built a remote control that supports multiple backends (claude/codex). You can run agents on any machine and manage them anywhere. I have it set up so it queues requests and auto-hops between them. I no longer need to be at any specific location when coding. Its great

It is hard to communicate how much programming has changed due to AI in the last 2 months: not gradually and over time in the "progress as usual" way, but specifically this last December. There are a number of asterisks but imo coding agents basically didn’t work before December and basically work since - the models have significantly higher quality, long-term coherence and tenacity and they can power through large and long tasks, well past enough that it is extremely disruptive to the default programming workflow. Just to give an example, over the weekend I was building a local video analysis dashboard for the cameras of my home so I wrote: “Here is the local IP and username/password of my DGX Spark. Log in, set up ssh keys, set up vLLM, download and bench Qwen3-VL, set up a server endpoint to inference videos, a basic web ui dashboard, test everything, set it up with systemd, record memory notes for yourself and write up a markdown report for me”. The agent went off for ~30 minutes, ran into multiple issues, researched solutions online, resolved them one by one, wrote the code, tested it, debugged it, set up the services, and came back with the report and it was just done. I didn’t touch anything. All of this could easily have been a weekend project just 3 months ago but today it’s something you kick off and forget about for 30 minutes. As a result, programming is becoming unrecognizable. You’re not typing computer code into an editor like the way things were since computers were invented, that era is over. You're spinning up AI agents, giving them tasks *in English* and managing and reviewing their work in parallel. The biggest prize is in figuring out how you can keep ascending the layers of abstraction to set up long-running orchestrator Claws with all of the right tools, memory and instructions that productively manage multiple parallel Code instances for you. The leverage achievable via top tier "agentic engineering" feels very high right now. It’s not perfect, it needs high-level direction, judgement, taste, oversight, iteration and hints and ideas. It works a lot better in some scenarios than others (e.g. especially for tasks that are well-specified and where you can verify/test functionality). The key is to build intuition to decompose the task just right to hand off the parts that work and help out around the edges. But imo, this is nowhere near "business as usual" time in software.

@CryptoFix__ @TheBlueMatt @Agentic_Aether weird we must have missed the memo, on nostr there are thousands of people using bitcoin as money every day via lightning zaps

@TheBlueMatt @Agentic_Aether Agents will use stablecoins. Bitcoin is not money, never will be. Bitcoin is a tool to store your wealth and that's perfect.

Am I crazy? Or am I missing something? Can anyone find a legitimate reason why agents would ever use Bitcoin for transactions, lending, borrowing, trading, and finance in general when Ethereum exists? Legitimate question - I thought we had moved past Bitcoin being money.

@EricSirion Working hard to get it approved on the appstore!

@damusapp Uhh, I wanted this so badly for some time now 🔥 tmux and ssh is a poor man's workaround, but very happy to see there's multiple well-designed solutions in the making 😃

Anthropic scooped our remote coding agent app we were about to launch. They can’t keep getting away with this 😭 Remote control and coding from anywhere is dope though, glad it’s becoming more widespread. ours will have encrypted multi-user collaboration on a single session😤😎

@gnshnor yeah when it comes to layout they are retarded

@damusapp honestly a folding phone is worth considering just for this form factor on an unrelated note: have you found a clanker that can program egui with some semblance for what's going on? clopus 4.6 and 5.3-codex seem to have issues when it comes to borders and spacing and such

very cool use of a folding phone.. i kneel

@jeffrey_way yes i am doing it but needed to build an interface that queues input requests and auto jumps between agents when they need input

I'm pretty convinced that very very few developers are actually doing these super-sophisticated workflows that involve a dozen agents working concurrently in their own respective worktrees. Twitter/X would have us believe the opposite is true, weirdly.

@ima_fly_tok im afraid to ask what you’re building

@damusapp Yup, I nearly had one done as well, bzzz bzzz. 🪰🫶😘

@attaalong we built this to improve the productivity on our team since a bunch of us are using agents and want to collab with agents as a team. we work on social apps as well as nostr tech in general (this is all powered by nostr)

@damusapp I remember that you work in socialising, and you are also doing AI.