One binary, that's awesome. So you decided to make a native ...

codonaft

npub1alptdev5srcw2hxg03567p4k6xs3lgj7f6545suc0rzp0xw98svse7rg94

hex

615a31c703c35482d10eb3ce0e44b7bc23279c4515cd340daa7ac8e5fe388d35

nevent

nevent1qqsxzk33cupux4yz6y8t8nswgjmmcge8n3z3tnf5pk484j89lcug6dgprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgswls4kuk2gpu89tny8c6d0q6mdrggl5f0ya226gwv833qhn8zncxgxhrnwc

Kind-1 (TextNote)

2026-05-13T21:39:10Z

↳ Reply to Peg Otis (npub1ngs4dyj46z36ne6lrh3wfjyrexlzu4s43plj9vhv76cczw7dtp7sf96dlu)

I have much to learn, now, if I'm going to make this truly offline-first. So far I've been hedging by saying just use any modern browser. The problem ...

One binary, that's awesome. So you decided to make a native app? Why deal with the web-based stuff at all then? Browser engines are coming with frustrating resources overhead IMO, with weird hacks (chrome://gpu) that eventually break due to some driver update. And the programming languages are quite... limited.

Do you still want to make it compatible with browsers for some reason? Or do you want to rely on Electron as something stable, that "just works" on major platforms? Or due to the existing code base?

Raw JSON

{
  "kind": 1,
  "id": "615a31c703c35482d10eb3ce0e44b7bc23279c4515cd340daa7ac8e5fe388d35",
  "pubkey": "efc2b6e59480f0e55cc87c69af06b6d1a11fa25e4ea95a439878c41799c53c19",
  "created_at": 1778708350,
  "tags": [
    [
      "e",
      "60312bff6758be42ca1c0c8780be54770f8778c131ca3f18248a627045d523f3",
      "wss://nos.lol",
      "root",
      "9a21569255d0a3a9e75f1de2e4c883c9be2e5615887f22b2ecf6b1813bcd587d"
    ],
    [
      "p",
      "9a21569255d0a3a9e75f1de2e4c883c9be2e5615887f22b2ecf6b1813bcd587d",
      "wss://relay.damus.io"
    ],
    [
      "client",
      "nosotros",
      "31990:c6603b0f1ccfec625d9c08b753e4f774eaf7d1cf2769223125b5fd4da728019e:1728437063755"
    ]
  ],
  "content": "One binary, that's awesome. So you decided to make a native app? Why deal with the web-based stuff at all then? Browser engines are coming with frustrating resources overhead IMO, with weird hacks (chrome://gpu) that eventually break due to some driver update. And the programming languages are quite... limited.\n\nDo you still want to make it compatible with browsers for some reason? Or do you want to rely on Electron as something stable, that \"just works\" on major platforms? Or due to the existing code base?",
  "sig": "fae6e75731be7649027b7083c7624821878043dcb79ab1ea9ab1a39d153a5e0336003f54b935bb3dc9d0a6885f5a2fc2887752cf62553ba564c54200e9e78df8"
}