yeah, i was shocked to learn from claude that sql injection ...

mleku

npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku

hex

502b56f2cebd504b00a9b7b219e84d7f0bf43c2fd548a5ffc6fc620dcafc7044

nevent

nevent1qqs9q26k7t8t65ztqz5m0vseapxh7zl58sha2j99llr0ccsdet78q3qprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsyeqqz27jc32pgf8gynqtu90d2mxztykj94k0kmttxu37nk3lrktc6xv3ac

Kind-1 (TextNote)

2026-02-24T08:23:31Z

↳ Reply to Troy (npub104zp04wlgddf0w84tj8jul3w75e7ydcuuhsull2etste5040xm2qg285rf)

And here I thought the lesson of the early 00's, that the UI should be separate from the business logic, was a basic understanding today. Maybe the te...

yeah, i was shocked to learn from claude that sql injection and buffer overflow vulnerabilities were still common. i was taught in 2013 to always sanitize all inputs, and i do it religiously, actually, often, excessively. in my code, more often bugs are from excessive checking.

and shit like rust's GC hinting system, and their tight coupling with 5 other elements of the syntax, mean it takes as long to compile it as it does parsing the object inheritance hierarchies of C++.

instead of buffer overflows, now you find rust code has protocol vulnerabilities instead. you can't blow up its memory anymore with crafted packets but instead you can break the state machines and cause them to fail or allow privilege escalations.

one step forward, two steps back, steadily as the languages get more "advanced" and "expressive" you see a concurrent escalation of complexity, which is hard to reason about.

i don't say "Golang or GTFO" for no reason. i go a lot further than some, with this, too, because i have identified about 6 separate things in Go's syntax that leads to frequent bugs. this is why i started building a fork of Go called "moxie" but actually...

now i am building a universal language processing system based on the cayley tree, meh, idc about these details anymore. i will push that into the mathematics of the memory of the system and you just write english and it generates binary code.

Raw JSON

{
  "kind": 1,
  "id": "502b56f2cebd504b00a9b7b219e84d7f0bf43c2fd548a5ffc6fc620dcafc7044",
  "pubkey": "4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f",
  "created_at": 1771921411,
  "tags": [
    [
      "e",
      "f456d28ec7b67a2ffef6a862a53dc0fec88a32297bb4f1b062ecfb524b36413b",
      "wss://nos.lol/",
      "root",
      "9233e12ac1d85a3ee9143b105a7053664f85e333dfc812cd638da44dc304e002"
    ],
    [
      "e",
      "78c8fee7bc95818332ea0472722bfdaf9ca853ff57b01fc4c91f2f43fab47f17",
      "wss://relay.primal.net/",
      "reply",
      "7d4417d5df435a97b8f55c8f2e7e2ef533e2371ce5e1cffd595c179a3eaf36d4"
    ],
    [
      "p",
      "7d4417d5df435a97b8f55c8f2e7e2ef533e2371ce5e1cffd595c179a3eaf36d4"
    ],
    [
      "client",
      "smesh",
      "https://smesh.mleku.dev"
    ]
  ],
  "content": "yeah, i was shocked to learn from claude that sql injection and buffer overflow vulnerabilities were still common. i was taught in 2013 to always sanitize all inputs, and i do it religiously, actually, often, excessively. in my code, more often bugs are from excessive checking.\n\nand shit like rust's GC hinting system, and their tight coupling with 5 other elements of the syntax, mean it takes as long to compile it as it does parsing the object inheritance hierarchies of C++. \n\ninstead of buffer overflows, now you find rust code has protocol vulnerabilities instead. you can't blow up its memory anymore with crafted packets but instead you can break the state machines and cause them to fail or allow privilege escalations.\n\none step forward, two steps back, steadily as the languages get more \"advanced\" and \"expressive\" you see a concurrent escalation of complexity, which is hard to reason about.\n\ni don't say \"Golang or GTFO\" for no reason. i go a lot further than some, with this, too, because i have identified about 6 separate things in Go's syntax that leads to frequent bugs. this is why i started building a fork of Go called \"moxie\" but actually... \n\nnow i am building a universal language processing system based on the cayley tree, meh, idc about these details anymore. i will push that into the mathematics of the memory of the system and you just write english and it generates binary code.",
  "sig": "f352514da09d30eab1d005f16d64a44d573fe5c2a7b0f7628e74346a5cc127c96d4590c11d6cd89266360fa38e297beb28b8f31b217a7b0686a4c87495ba940f"
}