.tpm i kitt.kitt add 自动延迟删除消息
return ['-1001771725356'].includes(msg.chatId.toString()) && ['/report'].includes(msg.text)
setTimeout(async () => { try { await msg.delete() } catch (e) {}; }, 15 * 1000);-1001771725356 的对话中延迟 15 秒删除 /reporttitle 或者 username, 类似这样: [`折腾啥`].includes(msg.chat.title) [`zhetengsha_group`].includes(msg.chat.username) .entity 命令
TeleBox 合集 
频道资源合集 
恰饭推荐 
群组
#TeleBox #Telegram #tg #人形自走机器人 #bot #插件 #脚本 #删除 #消息 #清理 #kitt #自动化 #延迟function operator(proxies) {
const withLatency = proxies.filter(p => p._latency !== undefined)
const withoutLatency = proxies.filter(p => p._latency === undefined)
withLatency.sort((a, b) => Number(a._latency) - Number(b._latency))
return [...withLatency, ...withoutLatency]
}
timeout 可适当调小, show_latency 节点名称加上延迟_latency 字段, 方便之后再处理
Sub-Store 多次检测节点延迟
Loon, 
Surge(ability=http-client-policy) Sub-Store 版本应 > 2.14.289HEAD 请求 10 次的延迟 Sub-Store 的默认配置 Sub-Store 脚本设置节点字段 _monitors$server._monitors = [
{
name: 'Cloudflare',
url: 'http://cp.cloudflare.com/generate_204',
method: 'HEAD',
number: 3,
timeout: 2000,
},
{
name: 'Google',
url: 'http://www.google.com/generate_204',
method: 'HEAD',
number: 3,
timeout: 2000,
},
]
好像是因为数据太大 如果在小组件直接请求实时数据就不显示了...
HTTP META 配合)timeout, concurrency 和 size 适当调节keep_incompatible 保留当前客户端不兼容的协议show_speed 显示速度. 默认不显示. 注: 即使不开启这个参数, 节点上也会添加一个 _speed 字段, 按速度倒序https://raw.githubusercontent.com/xream/scripts/main/surge/modules/sub-store-scripts/check/speed.js#keep_incompatible=true&show_speed&size=10&timeout=10000&concurrency=1
2. Node.js 版(需要 HTTP META 配合)https://raw.githubusercontent.com/xream/scripts/main/surge/modules/sub-store-scripts/check/http_meta_speed.js#keep_incompatible=true&show_speed&size=10&timeout=10000&concurrency=1&http_meta_protocol=http&http_meta_host=127.0.0.1&http_meta_port=9876&http_meta_start_delay=3000&http_meta_proxy_timeout=10000 Sub-Store 合集 频道资源合集 恰饭推荐 群组 #Sub-Store #SubStore #脚本 #节点 #订阅 #节点测速 #测速 #节点延迟 #延迟 #检测 #check #HTTP-META #HTTPMETA #Meta #Clash #脚本 #Node #服务器 #VPSHTTP META 配合)timeout 可适当调小, keep_incompatible 保留当前客户端不兼容的协议, show_latency 节点名称加上延迟url 需要 encodeURIComponent. 默认 http://connectivitycheck.platform.hicloud.com/generate_204status 合法的状态码的表达式. 需要 encodeURIComponent . 默认 204http://223.6.6.6 状态码 404: url=http%3A%2F%2F223.6.6.6&status=404节点操作 - 脚本操作 中 选择 链接https://raw.githubusercontent.com/xream/scripts/main/surge/modules/sub-store-scripts/check/availability.js#show_latency=true&keep_incompatible=true&status=204&url=http%3A%2F%2Fconnectivitycheck.platform.hicloud.com%2Fgenerate_204&timeout=1000&retries=1&retry_delay=1000&concurrency=10
2. Node.js 版(需要 HTTP META 配合):https://raw.githubusercontent.com/xream/scripts/main/surge/modules/sub-store-scripts/check/http_meta_availability.js#show_latency=true&keep_incompatible=true&status=204&url=http%3A%2F%2Fconnectivitycheck.platform.hicloud.com%2Fgenerate_204&timeout=1000&retries=1&retry_delay=1000&concurrency=10&http_meta_protocol=http&http_meta_host=127.0.0.1&http_meta_port=9876&http_meta_start_delay=3000&http_meta_proxy_timeout=10000 Sub-Store 合集 频道资源合集 恰饭推荐 群组 #Sub-Store #SubStore #脚本 #节点 #订阅 #测活 #节点测活 #节点延迟 #延迟 #检测 #check #HTTP-META #HTTPMETA #Meta #Clash #脚本 #Node #服务器 #VPS