IDKWID¯\_(ツ)_/¯WDIM

i like that web browsers are silly this week.

i've become a fortune cookie.

we are going to design systems that outpace our ability to build them. a queue of breakthrough innovations.

Redstar Rising

it takes a lot and then some to impress these days. all or nothing.

engineer it so the LLM mostly sits on the bench. is where we are at. finally.

Stop caring so much about model releases. Focus on the harness, and improving the environment your agent operates in. You'll find yourself far ahead of the curve.

helluvajev

Only had it 1 hour, but whaaaat this speak and spell is insane

process of self-elimination.

monetized unwillingness.

Please don't install - it's trivial to turn Muse into the ultimate backdoor 💀👀 Ya, as an AI assistant built to manage your Mac, Muse needs broad access to your digital life. But serious 0-day flaw(s) can let local malware/attackers invisibly hijack it. Let me show you. 🧵

pattern recognition. pattern demolition.

what if we ourselves are the recursive self-improving AGI?

omarchy's transmedia cousin.

it's high time to build out the metaverse. again.

sharing some notes on typesafe 🤝 coding agents: docs.google.com/document/d/1… we likely will never have time (ever again) to play ourselves, but hope the that the community goes WILD (and makes me look like a naive idiot)

@Cloudflare is back on its localhost meet the Internet tour. One command. Instant trycloudflare.com URL. No account. No DNS. JSON for the agents. People are posting it like they invented remote access. Here is what that command actually does. Your laptop dials Cloudflare. TLS dies at their edge. They get to see the request. Then they send it down their tunnel to cloudflared, which often talks to your app over plain HTTP on 127.0.0.1. You did not punch a hole in NAT. You handed a CDN the plaintext and asked it to be nice. The cute parts they leave out: Quick tunnels cap at 200 concurrent requests and choke on SSE. Kill the process and the hostname dies with it. Google already indexes trycloudflare.com. Devs are searching site:trycloudflare.com and peeking at other people's live localhost apps. Random words in a URL are not a lock. And because malware crews already burned that domain, half the corporate networks just block it outright. Your share this with anyone link dies in the first office Wi-Fi it hits. Named tunnels do not fix the architecture. Now they own the DNS, the cert, the access policy, and whether the box even exists today. Their outage or their account flag and every service behind that tunnel goes dark. Including the one sitting next to you. If you are demoing a toy page for five minutes, whatever. If that port has webhooks, secrets, SSH, a dashboard, photos, a game server, Docker, anything you would not paste into a support ticket, stop renting a spyglass so you can share localhost. Holesail does the job without the hostage situation. holesail --live 8000 You get an hs:// key. Other side runs holesail hs://... and you are on the same port from anywhere. Discovery is HyperDHT. NAT gets holepunched. After that the bytes go peer to peer. Noise handshake. Encrypted stream. No relay tasting the traffic. No account. TCP and UDP. Bandwidth is whatever your ISP already sold you. Cloudflare is great at being a giant reverse proxy. That is the product. They will keep making the one-liner smoother because agents need a public URL and Cloudflare wants to own the pipe. You do not need their pipe. One key. Two machines. Direct. Encrypted. Nobody in the middle protecting you by reading it. holesail.io github.com/holesail/holesail

The open source internet is here... piped.video/5vbl5FL-nsI

its increasingly important to do all of your computing on linux.