nico v20240323

https://github.com/txthinking/nico

- Support CAC

Get $10-$50 AI balance

https://forms.gle/kjR5MccgzvGFGPp57

# Brook v20240606

## CLI

- Each subcommand has a --example argument, for example brook server --example
- brook link --token: A token represents a user's identity. A string encoded in hexadecimal. Server needs to have --userAPI enabled. Note that: Only supported by the brook GUI(except for OpenWrt) and tun2brook. However, it is more recommended to use the user system to build token with brook link, such as brook-user-system.
- brook --userAPI: When you build your own user system, Brook Server will send GET request to your userAPI to check if token is valid, for example: https://your-api-server.com/a_unpredictable_path. Yes, it is recommended to add an unpredictable path to your https API, of course, you can also use the http api for internal network communication. The request format is https://your-api-server.com/a_unpredictable_path?token=xxx. When the response is 200, the body should be the user's unique identifier, such as user ID; all other status codes are considered to represent an illegitimate user, and in these cases, the body should be a string describing the error. It should be used with --serverLog and server/wsserver/wssserver/quicserver with brook protocol. For more information, please read https://github.com/txthinking/brook/blob/master/protocol/user.md
- brook --userAPIValidCacheTime: Once a token is checked and valid, the userAPI will not be requested to validate again for a certain period (s). A reasonable value must be set, otherwise it will affect the performance of each incoming connection (default: 3600)
- brook --userAPIInvalidCacheTime: Once a token is checked and invalid, the userAPI will not be requested to validate again for a certain period (s). A reasonable value must be set, otherwise it will affect the performance of each incoming connection. Note that this may affect the user experience, when you change the user status from invalid to valid in your user system. (default: 1800)
- brook --tag: Tag can be used to the process, will be append into log or serverLog, such as: 'key1:value1'. All tags will also be appended as query parameters one by one to the userAPI
- brook --pid: A file path used to store pid. Send SIGUSR1 to me to reset the --serverLog file on unix system
- brook --blockDomainList: One domain per line, suffix match mode. https://, http:// or local file absolute path. Like: https://raw.githubusercontent.com/txthinking/brook/master/programmable/list/example_domain.txt. Works with server/wsserver/wssserver/quicserver
- brook --blockCIDR4List: One CIDR per line, https://, http:// or local file absolute path, like: https://raw.githubusercontent.com/txthinking/brook/master/programmable/list/example_cidr4.txt. Works with server/wsserver/wssserver/quicserver
- brook --blockCIDR6List: One CIDR per line, https://, http:// or local file absolute path, like: https://raw.githubusercontent.com/txthinking/brook/master/programmable/list/example_cidr6.txt. Works with server/wsserver/wssserver/quicserver
- brook --blockGeoIP: Block IP by Geo country code, such as US. Works with server/wsserver/wssserver/quicserver
- brook --blockListUpdateInterval: Update list --blockDomainList,--blockCIDR4List,--blockCIDR6List interval, second. default 0, only read one time on start (default: 0)
- brook link --udpoverstream: When server is brook quicserver, UDP over Stream. Under normal circumstances, you need this parameter because the max datagram size for QUIC is very small. Note: only brook CLI and tun2brook suppport for now (default: false)

## GUI

- support brook link --fragment
- support brook link --token. However, it is more recommended to use the user system to build token with brook link, such as brook-user-system
- Fake DNS and Block Google Secure DNS module have been enabled by default.

## tun2brook v20240607

https://github.com/txthinking/tun2brook

## Documentation

https://brook.app

Because Google plans to shut down the Cloud Source Repositories service on June 17, 2024, I have to migrate the existing build system. During this process, there may be some fluctuations in the api of my products, for which I apologize. I will carry out the migration in small steps to keep the fluctuations to a minimum.

How to Use Shiliew to Unlock TikTok

https://www.txthinking.com/talks/articles/shiliew-tiktok-en.article

如何使用 Shiliew 解锁 TikTok

https://www.txthinking.com/talks/articles/shiliew-tiktok.article

zhen renamed to z, and open source and free. If you like joker, you may like z too. 🤟

mad v20240923

https://github.com/txthinking/mad/releases/tag/v20240923

- bugfix
- add mad ca --start: Certificate valid start time, such as: '2024-09-22T13:07:38+08:00'. If empty, it is the current time
- add mad ca --end: Certificate valid end time, such as: '2024-09-22T13:07:38+08:00'. If empty, it is start time add 10 years
- add mad cert --start: Certificate valid start time, such as: '2024-09-22T13:07:38+08:00'. If empty, it is the current time
- add mad cert --end: Certificate valid end time, such as: '2024-09-22T13:07:38+08:00'. If empty, it is start time add 10 years
- Deprecated: mad cert --ca_key
- add mad cert --caKey: ROOT Key file path (default: "ca.key.pem")
- add mad cert --commonName: If empty, the first domain or IP will be used

sshexec v20240925

https://github.com/txthinking/sshexec

- --sudo: run command with sudo, does not apply to download and upload (default: false)
- exit code 1 if something wrong

z v20240927

https://github.com/txthinking/z

- optimize auto-start on boot under certain systems
- bugfix

brook-store v20241012

https://github.com/TxThinkingInc/brook-store/releases/tag/v20241012

## Before upgrade

- stop brook-user-system first
- upgrade sshexec: nami install sshexec
- install brook-store: nami install brook-store

## Run it

joker brook-store

## Changes

- brook-user-system renamed to brook-store, don't worry, they still use the same database $HOME/.brook.db
- Enable sqlite WAL mode, this will enhance write performance and will add two files. After running for a period of time, check: ls $HOME/.brook.db*
- Run task in a new worker thread
- Support Product and product payment link
- Support reCAPTCHA, if you enable public signup, recommend enable reCAPTCHA to prevent malicious registrations from writing to the database. Or disable signup, and create new user account from admin
- Support Site Description, you can use this to describe your service
- UI update
- And other much more updates, see the tips on some admin pages
- bugfix: build.sh

> BTW, if you want to eliminate the 30-minute lockout period for users from expiration(or others) to recovery, you can disable the brook experimental option brook --userAPIInvalidCacheTime 0

### Online

https://cheap.shiliew.com

It has been running for two weeks.