https://blog.glyphdrawing.club/font-with-built-in-syntax-highlighting/

https://platform.deepseek.com/api-docs/zh-cn/function_calling/

• https://stackoverflow.com/questions/30441025/read-all-text-from-stdin-to-a-string
• https://stackoverflow.com/questions/3515208/can-colorized-output-be-captured-via-shell-redirect

pipe.js:

process.stdout.write(require('fs').readFileSync(0, 'utf-8'))
// or process.stdin.pipe(process.stdout)

script -q /dev/null node -p  "Boolean(0)" | node pipe.js
# will print yellow false

https://stablediffusion3.net/zh-CN

啥叫递归啊

url to text(for llm

• https://r.jina.ai/https://github.com/jina-ai/reader
• https://r.jina.ai/https://bb.viegg.com/p/1348

• https://transformer-circuits.pub/
• https://distill.pub/

我才知道娜塔丽波特曼是犹太人……还有她今年离婚了。。😅

=== update ===

才注意到原来费曼也是犹太人😭

let a = await (Promise.reject('msg')).catch(e => e)
a === 'msg' // true

(但如果把await放到括号里面就catch不住了🙅‍♀️

node从v18起就支持把JS代码打包成二进制了：https://nodejs.org/api/single-executable-applications.html

（我记得好像记录过这个，但是找不到了...😅😅

成功用workerd把gdshare在vps上跑起来了

• https://github.com/cloudflare/workerd/blob/main/samples/helloworld/README.md
• https://github.com/Dcard/docker-workerd

docker pull dcard/workerd

docker run -d -p 8081:8081 -v .:/app dcard/workerd serve /app/workerd.capnp

第二条命令执行的时候要确保当前目录有两个文件，一个是workerd.capnp:

using Workerd = import "/workerd/workerd.capnp";

const helloWorldExample :Workerd.Config = (
  services = [ (name = "main", worker = .helloWorld) ],
    sockets = [ ( name = "http", address = "*:8081", http = (), service = "main" ) ]
);

const helloWorld :Workerd.Worker = (
  serviceWorkerScript = embed "worker.js",
  compatibilityDate = "2023-02-28",
);

另一个是worker.js

addEventListener('fetch', event => {
  event.respondWith(handle(event.request));
});

async function handle(request) {
  return new Response("Hello World\n");
}

（实际上我是用了gdshare

其实不一定要用docker，我本地迷你主机就成功用官方发布的二进制的workerd跑起来了，但是我的vps ubuntu版本比较老，直接跑二进制会报错……

具体命令则是 ./workerd serve workerd.capnp

老版本的node（比如8）在请求用let's encrypt的https证书加密的网站时会报错certificate has expired

有几种解决办法，最正确的是升级node版本，我试了下14就不报错了。。
最省事的是在env里加一句NODE_TLS_REJECT_UNAUTHORIZED=0

更灵活点可以在具体的请求里忽略tls报错：

const https = require("https");

const agent = new https.Agent({
  rejectUnauthorized: false,
});

最硬核的就是改node源码自己编译了。。

HTTP 418 I'm a teapot

辣鸡google把搜索结果里的cache链接给去掉了，真不知道怎么想的……

不过目前还可以通过构造链接的方式查看缓存，比如 https://webcache.googleusercontent.com/search?q=cache:https://bb.viegg.com/