leafac

- `application/x-www-form-urlencoded`
  - `URLSearchParams`
  - <https://github.com/expressjs/body-parser>.
- `multipart/form-data`
  - <https://github.com/mscdex/busboy>.
    - <https://github.com/expressjs/multer>.
    - <https://github.com/richardgirges/express-fileupload>.
  - <https://github.com/node-formidable/formidable>.
    - Does too much (plugins, and so forth).

• .

leafac

• autocannon uses negligible CPU.

• Use yes > /dev/null to saturate one core.

• Stats shows an aggregate of all the CPU cores, just like the Activity Monitor lower pane. So if 1 out of 8 cores is saturated, you see 25% usage.

• In a Mac Mini with a M1 processor, the performance cores saturate first and the efficiency cores saturate last.

• Sending signals:

  ⌃C	SIGINT

| kill, Activity Monitor > Quit, Stats > Kill process, and so forth | SIGTERM |

leafac

• Worker threads
  • “Workers (threads) are useful for performing CPU-intensive JavaScript operations. They do not help much with I/O-intensive work. The Node.js built-in asynchronous I/O operations are more efficient than Workers can be.”
  • “Unlike child_process or cluster, worker_threads can share memory.”
  • But they can’t share server ports and they don’t come with load balancing
• https://www.npmjs.com/package/workerpool
  • Manage pool of workers (I suppose in case of crashes and things like that)
  • Makes it easier to pass values from and to worker
  • Makes it easier to define worker code inline, but the usefulness of that is limited, because it isn’t a real closure
• https://www.npmjs.com/package/piscina
• Less magical than workerpool, just handles pool

leafac

leafac

Teachable Machine

• https://teachablemachine.withgoogle.com/
• Approaches
  • Use Sharp and generate input tensors by hand
  • Use browser simulators
    • https://github.com/SashiDo/teachablemachine-node/
      • https://blog.sashido.io/how-to-load-a-teachable-machine-image-model-in-a-node-js-project/
    • https://github.com/googlecreativelab/teachablemachine-community
• https://github.com/drinkspiller/teachablemachine-node-example/

leafac

• Diagnostics tools
  • https://samltool.io/ is good for inspecting SAML requests and responses, but don’t trust its signature validation (keycloak/keycloak#22962)
  • https://www.samltool.com/online_tools.php is good for verifying signatures, but doesn’t show you the decoded request/response
• One key
  • https://www.stackallocated.com/blog/2020/saml-idp-no-shared-keys/
  • All Identity Providers
  • All purposes: signing & encrypting
  • All services: SAML & LTI (OAuth)
  • But metadata is different, because we use the URL to communicate the Identity Provider samlIdentifier, which is necessary to pick up the idpIssuer before we even decode the SAML Response.
• Pros of separate keys:

leafac

• Testing tools
  • Lightweight
    • https://github.com/mcguinness/saml-idp
    • https://github.com/boxyhq/mock-saml
    • https://github.com/Clever/saml2
    • https://github.com/auth0/node-samlp
    • https://github.com/bjorns/mock-idp
  • Enterprisy
    • https://www.shibboleth.net
• https://www.keycloak.org

leafac

• https://css-tricks.com/the-current-state-of-styling-scrollbars-in-css/
• https://css-tricks.com/custom-scrollbars-in-webkit/
• https://css-tricks.com/almanac/properties/s/scrollbar/
• https://caniuse.com/css-scrollbar
• https://www.digitalocean.com/community/tutorials/css-scrollbars
• Firefox
  • https://css-tricks.com/almanac/properties/s/scrollbar-color/
• https://css-tricks.com/almanac/properties/s/scrollbar-width/

leafac

The best solution is to roll it out by hand, not using a library and not using the Drag-and-Drop API.

---

• https://github.com/SortableJS/Sortable
  • Uses Drag-and-Drop API, so doesn’t let you customize the cursor
• https://github.com/bevacqua/dragula
  • Doesn’t work on mobile
• Drag-and-Drop API

leafac

- Use Got hook
- Use Transform in pipeline

• Approaches
  • Question about current approach: sindresorhus/got#2060
  • Alternative approach that doesn’t work: Using Caddy. That would be nice because it would reduce the load on the application. But it could be limiting moving forward because it’d be more difficult to do HMAC, and so forth. But none of this matters, Caddy doesn’t seem to support proxying to arbitrary upstreams.
  • Alternative approach: Use a standalone image proxy & fire it up behind Caddy, alongside the main application.
  • Alternative approach: await on headers & only pipe the body?
    • response.set(msg.headers);
    • https://github.com/sindresorhus/got/commit/83bc44c536f0c0ffb743e20e04bf569c51fa5d69
• Tests: