cho.sh
2,244 notes
Liked on XI made a mistake. When Jack and I decided to organize this $100K Hackathon, my biggest concern was cheating. Unlike a regular hackathon, everyone participates from home. And because the winner is whoever makes the most PROFIT (not revenue), there are so many ways to manipulate the numbers. So I added a $99 entry fee. One thing I’ve learned from building businesses is that people tend to be more committed when they pay for something. I thought it would filter out spam, attract serious builders, and make the competition fairer for everyone. But I completely missed the other side. 3 years ago, I was a living with my apps. Today, I’m financially free. My life changed so much that somewhere along the way, I lost perspective on what $99 means to someone else. For someone in India, someone struggling to pay their bills, or someone trying to make their first dollar online, $99 can be a lot of money. And those are exactly the people I want to help! I’ve spent years sharing what I’ve learned, reviewing random people’s landing pages, and organizing free meetups around the world. Not because there’s money to make, but because I genuinely love seeing people build things and succeed. And somehow, I was so focused on keeping cheaters out that I didn’t realize I was also keeping genuine builders out. That’s my mistake. So I’ve decided to make the $100K Hackathon completely FREE :) Everyone who already paid got a full refund. I’m still worried about cheating. That problem hasn’t disappeared, and Jack and I will have to figure out better ways to verify profits and keep the leaderboard fair. But that’s our problem to solve. Thank you to everyone who shared their thoughts. Sometimes you need people to remind you of things you’ve forgotten. I genuinely hope this hackathon changes someone’s life. ❤️Liked on XIt’s time to bring back Cafe CursorPosted on Xyo @pendev i can't live share edit a .pen file? it's the most needed featurePosted on XI'm coining a word "Agentsplaining" Agents condescendingly assuming the user don't know fuck and repeating the obviousReplied on X@jayhxmo @raycast Hard to explain. It's the small detailsPosted on X@raycast iOS keyboard is insanely good. Might resub Raycast pro just cuz of thisReplied on X@ishuagra02 I saw a theory that F5.2 is a post train of 5.1, but O5.5 is a distillation of F5.5(unreleased new pretrain) and thats why O5.5 > F5.2Liked on X@anaclumos don't know what is actually improved 👀Posted on Xam i the only one underimpressed with 5.2 fableReplied on X@bvvst great minds think alike https://t.co/YRFWhb1mcOLiked on XClaude Fable 5.2 is out and it's the perfect time to run this god-level prompt on your codebase: "I want you to audit our codebase, is anything here unnecessary, overly complicated in our current setup, or based on weak assumptions? Challenge them. - What can be deleted entirely? - What can be simplified now that unnecessary pieces are gone? Then make the changes. Prefer deleting over simplifying, simplifying over optimizing, and optimizing over automating. This product is being used by thousands of customers, do not cut any corners." This prompt is one I run often and leads to the best results.Replied on X@akshayadinesh19 @bot can we please BYOM for botsLiked on XTo be fair, the Chinese models have a much lower refusal rateLiked on XF*CK IT, im creating a library of AI slop indicators. my feed is full of taste larpers. stay tuned https://t.co/5Muv8nQRm3Liked on XJENSEN! THATS NOT WHAT WE MEANT BY CHINESE MODELS!!!!!!!Liked on Xmy parents had to declare bankruptcy when I was a kid, so they had every reason to pressure me towards a more stable career path instead, they were so patient with me, even as i failed startup after startup for years so getting to tell my mom that everything turned out okay was a really special moment :) for those who can't read Korean, her first message roughly translates to: "Really!!! Congratulations my son. So much :') Thank you God!" i know I've been posting about my exit for like a week now, but it really is a big deal for me and my family! i'll share more about how this all happened and some tactical advice later this week, but for now i'm just riding out all the emotions to quote my mom, thank you God!!!!Liked on X@thefarmers_Dog it stands for Egg GzampleLiked on X🦍 Introducing Memorilla: memory as a modality for LLMs Memorilla turns everything a frozen LLM needs to remember into just 16 memory embeddings ⚡ It uses up to 4,212× fewer tokens and is 27× faster than full context inference while more accurate 🎯 Pushes the Pareto frontier over RAG and agentic memory in personalization, long-document and knowledge QA A thread 🧵:Liked on XThere's a huge product opportunity downstream of Tailscale etc too. At @tldraw we've started designing for "high trust networks" and it's been a beautiful thing. 1. Features that would be a nightmare on the internet are okay on my computer and mostly okay on private networks. Websites that execute user-generated scripts, control production systems, allow for users to send desktop notifications, spend tokens, or directly prompt my agent. Crazy stuff that would only make sense if everyone was in a committed polycule. 2. When everyone on the server can be trusted to have _external_ reasons for good behavior (eg keeping their job, or maintaining friends, family, church, mafia org), the software can be designed in a default social way. Most apps default to isolation, low horizontal visibility, highly restricted collaboration. Makes sense if the social contracts are inside of the app, but if you can trust that they live outside of the app then you can get wild. Example being small group chat names as an emergent comedy phenomenon because anyone in the group can change the name. 3. This can work for commercial products, too, not just internal stuff. Security matters more than ever but the way we've seen that manifest is that more companies are more confident in their own solutions than anything we could provide, to the point where owning data and access is a better value proposition than having it managed. Always has been true for big companies but now even small companies can get a good secure network set up pretty easily, and the hooks we need to build are easy enough. tldraw offline got us started down this road (and shout out to @pendev for first introducing me to the idea of desktop + mcp). We've been bringing that product to private networks and it's been exciting to see how much we can get away with. Keep an eye outReplied on X@saradu birds eye viewLiked on XApplications close in 2 days!! If you have a cool bio idea, and $5-10k will go a long way for you, please apply!!! https://t.co/NCvmrNC53cLiked on XWe've been early adopters of Rust since 2018 and a lot of our infra, voice tech, and even some of the current client is already Rust, the holy grail was getting the whole client there. That means Electron goes away, and so does React Native, mobile keeps native UI but shares app code with desktop via Rust. We hope to get it into testing with users soon™. (And it's not Tauri, it's GPUI, so good guess everyone.) Alright, back to staring at the WoW Forever login screen.Reposted on XOh boy. https://t.co/X7SSskGuGvLiked on XRIP .si domain squatters
Providing DOM API to Worker Threads

Providing DOM API to Worker Threads

Warning

Over a year old. May be outdated

Objective

  • Provide synchronous DOM API Access to Web Worker Threads
  • Part of

Start

html
<!doctype html>
<html lang="en">
  <head>
    <meta charset="UTF-8" />
    <meta http-equiv="X-UA-Compatible" content="IE=edge" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <title>Document</title>
    <script>
      const myWorker = new Worker("worker.js");
      myWorker.onmessage = function (e) {
        console.log(`Worker said : ${e.data}`);
      };
      function msg() {
        myWorker.postMessage("MAIN");
      }
    </script>
  </head>
  <body>
    <h1>Hello</h1>
    <button id="btn" onclick="msg()">Communicate with worker</button>
  </body>
</html>
js
postMessage("Worker is ready!");

onmessage = function (e) {
  console.log("WORKER.onMessage:", e.data);
  postMessage(`I am a worker. Hello, ${e.data}.`);
};

The type of e is MessageEvent.

MessageEvent - Web APIs.

Synchronous Call from Main

To enable , we need a secure context crossOriginIsolated.

By default, crossOriginIsolated is false.

To set crossOriginIsolated to true, we need two headers.

Tim already built a super easy toolkit that sets both headers to the desired values.

Then we only need to

D351D6

This is so cool.

84C1D5

2968C0

Save Point 1

html
<!doctype html>
<html lang="en">
  <head>
    <meta charset="UTF-8" />
    <meta http-equiv="X-UA-Compatible" content="IE=edge" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <title>Document</title>
    <script>
      console.log("crossOriginIsolated", crossOriginIsolated);

      // defining SAB and sending it to the worker
      const sab = new SharedArrayBuffer(1024);
      const int32 = new Int32Array(sab);
      const myWorker = new Worker("worker.js");

      function syncSab() {
        myWorker.postMessage({
          type: "init",
          sab: sab,
        });
      }

      myWorker.onmessage = function (e) {
        console.log(`Worker said : ${e.data}`);
      };

      function increment() {
        // ↓ Same as int32[0]++, but Thread Safe
        Atomics.add(int32, 0, 1);
        Atomics.notify(int32, 0);
      }

      function freeze() {
        // Sets [0] to 0.
        // the heartbeat function waits if [0] is 0.
        Atomics.store(int32, 0, 0);
      }
    </script>
  </head>
  <body>
    <h1>RPC Demo</h1>
    <button id="syncSab" onclick="syncSab()">Send SAB to Worker</button>
    <button id="increment" onclick="increment()">Increment</button>
    <button id="freeze" onclick="freeze()">Freeze</button>
  </body>
</html>
js
postMessage("Worker is ready!");

let sab = undefined;
let int32 = undefined;

onmessage = function (e) {
  console.log("WORKER.onMessage:", e.data);
  if (e.data?.type === "init") {
    sab = e.data.sab;
    int32 = new Int32Array(sab);
    console.log("Received SAB");
    Atomics.wait(int32, 0, 0);
    heartbeat();
  }
  postMessage(`I am a worker. Hello, ${JSON.stringify(e.data)}.`);
};

function heartbeat() {
  setInterval(() => {
    Atomics.wait(int32, 0, 0); // doesn't beat if [0] is 0
    console.log("WORKER.heartbeat:", Atomics.load(int32, 0));
    Atomics.add(int32, 0, 1);
  }, 1000);
}
  • Sends when clicking the Send SAB to Worker button.
    • [0] is set to zero, so the heartbeat function waits.
  • If Increment button is clicked, [0] is no longer 0.
    • We then notify any function waiting at [0].
  • heart starts beating, incrementing [0].

DDD712

Remote Procedure Call

  • See Remote procedure call
  • RPC is a request-response protocol. An RPC is initiated by the client, which sends a request message to a known remote server to execute a specified procedure with supplied parameters. The remote server sends a response to the client, and the application continues its process. While the server is processing the call, the client is blocked (it waits until the server has finished processing before resuming execution) unless the client sends an asynchronous request to the server, such as an XMLHttpRequest.

Note that

  • main only notify().
  • main never wait().
  • worker will yield to wait().

Complete

EAB9DE

Voila! I have created a synchronous polyfill layer for window.prompt and window.innerHeight functions inside a worker.

html
<!DOCTYPE html>
<html lang="en">
  <head>
    <meta charset="UTF-8" />
    <meta http-equiv="X-UA-Compatible" content="IE=edge" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <script src="./status.js"></script>
    <title>Worker RPC/title>
    <script>
      console.log('crossOriginIsolated', crossOriginIsolated)
      const Status = {
        UNINITIALISED: 0,
        READY: 1,
        COMPLETED: 2,
        ERROR: 3,
      }
      const worker = new Worker('worker.js')
      worker.onmessage = function (e) {
        const message = e.data
        if (message?.func === 'prompt') {
          const sab = message?.sharedArrayBuffer
          const int32 = new Int32Array(sab)
          const ans = prompt(message?.msg)
          if (ans) {
            const enc = new TextEncoder()
            const buf = enc.encode(ans)
            int32.set(buf, 0)
            Atomics.notify(int32, 0, 1)
          }
        } else if (message?.func === 'windowInnerWidth') {
          const sab = message?.sharedArrayBuffer
          const int32 = new Int32Array(sab)
          int32.set([window.innerWidth], 0)
          Atomics.notify(int32, 0, 1)
        }
      }
    </script>
  </head>
  <body>
    <h1>Worker RPC Demo</h1>
    <button onclick="console.log('hello')">Console Log</button>
    <button onclick="console.log('main thread:', window.innerWidth)">
      Console Log Window Inner Width
    </button>
  </body>
</html>
js
const Status = {
  UNINITIALISED: 0,
  READY: 1,
  COMPLETED: 2,
  ERROR: 3,
};

function sleep(ms) {
  const end = Date.now() + ms;
  while (Date.now() < end) {}
  return Date.now();
}

// polyfill layer for Worker.Prompt
function prompt(msg) {
  const sab = new SharedArrayBuffer(1024);
  const int32 = new Int32Array(sab);
  Atomics.store(int32, 0, Status.READY);
  postMessage({
    sharedArrayBuffer: sab,
    func: "prompt",
    msg: msg,
  });

  // Waiting
  Atomics.wait(int32, 0, Status.READY);

  // Waiting complete, get the result
  const ab = new ArrayBuffer(sab.byteLength);
  const view = new Uint8Array(ab);
  view.set(new Uint8Array(sab));
  const decoder = new TextDecoder();
  const string = decoder.decode(view);
  console.log("WORKER recieved result:", string);
}

const window = {
  get innerWidth() {
    const sab = new SharedArrayBuffer(4);
    const int32 = new Int32Array(sab);
    Atomics.store(int32, 0, Status.READY);
    postMessage({
      sharedArrayBuffer: sab,
      func: "windowInnerWidth",
    });
    Atomics.wait(int32, 0, Status.READY);
    const innerWidth = Atomics.load(int32, 0);
    return innerWidth;
  },
};

// Therefore we can...

sleep(5000);

prompt("hello!");

sleep(2000);

console.log("worker thread:", window.innerWidth);

console.log(
  "this should go after printing worker window.innerWidth (sync access)",
);

// This all happens synchronously in multi-thread.
Backlinks4