Kai kaichen

Introduction

Apple restricted the access to Xcode LLM (Predictive code completion) feature on China models of Mac. This guide provides a way to bypass that restriction. It's verified on macOS 15.0 Beta (24A5264n), but there is no guarentee that it will always work on later macOS versions.

Prerequisites

Xcode is installed and run at least once.
SIP debugging restrictions are disabled (via csrutil enable --without debug command in recovery mode).

Disclaimer

Warning

The following guide need to disable SIP to work.

Please confirm the risk of disabling the SIP by yourself.

Another solution which does not require disabling SIP is currently under investigation.

Step 0

Reboot into Recovery OS + Disable SIP

Purpose

Bootstrap knowledge of LLMs ASAP. With a bias/focus to GPT.

Avoid being a link dump. Try to provide only valuable well tuned information.

Prelude

Neural network links before starting with transformers.

Recently Executed Contracts with Issues in EIP 1884

Background

EIP 1884 is set to be implemented into the upcoming Ethereum 'Istanbul' hard fork. It

increases the cost of opcode SLOAD from 200 to 800 gas
increases the cost of BALANCE and EXTCODEHASH from 400 to 700 gas
adds a new opcode SELFBALANCE with cost 5.

OP_CHECKDATASIG

OP_CHECKDATASIG and OP_CHECKDATASIGVERIFY check whether a signature is valid with respect to a message and and a public key. The message is restricted to exactly 256 bits, if longer messages are to be signed, it is recommended to sign the messages hash.

OP_CHECKDATASIG permits data to be imported into a script, and have its validity checked against some signing authority such as an "Oracle".

OP_CHECKDATASIG and OP_CHECKDATASIGVERIFY are designed to be implemented similarly to OP_CHECKSIG [1]. Conceptually, one could imagine OP_CHECKSIG functionality being replaced by OP_CHECKDATASIG, along with a separate Op Code to create a hash from the transaction based on the SigHash algorithm.

The Story of NPM and Yarn

In the beginning there was NPM, and for a time it was good. Packages went forth and multiplied. The New Gods proclaimed the great demon Dependency Management had been slain. But The Old Gods knew better, for they had seen much and knew that the demon can never be killed, only held at bay.

The Old Gods were ignored. In the folly of a young age grew an abundance of packages and with them grew the scourge of dependency. In the depths beneath the earth, in a place beyond memory, the great demon stirred.

The first sign something was wrong was non-deterministic package version mismatches. “This is fine!” The New Gods declared. “A temporary setback, nothing more! We can fix it.” And so they introduced shrinkwrap, a lamp to combat the growing darkness.

But it proved to be too little, too late, and dusk continued to fall. The New Gods suffered their first major defeat at the [Battle of Left-pad](https://www.theregister.co.uk/2016/03/23/npm_left_

A top-down look into Elixir (for Rubyists)

Phoenix (as "Rails for Elixir")
- Rails and Phoenix can get suspiciously similar
- A code sample:
controller.rb

	Begin by enclosing all thoughts within <thinking> tags, exploring multiple angles and approaches.
	Break down the solution into clear steps within <step> tags. Start with a 20-step budget, requesting more for complex problems if needed.
	Use <count> tags after each step to show the remaining budget. Stop when reaching 0.
	Continuously adjust your reasoning based on intermediate results and reflections, adapting your strategy as you progress.
	Regularly evaluate progress using <reflection> tags. Be critical and honest about your reasoning process.
	Assign a quality score between 0.0 and 1.0 using <reward> tags after each reflection. Use this to guide your approach:

	0.8+: Continue current approach
	0.5-0.7: Consider minor adjustments
	Below 0.5: Seriously consider backtracking and trying a different approach

	class EOSKey {
	// Generate EOS owner pk and active pk from mnemonic
	private static List<byte[]> calcDefaultKeys(List<String> mnemonics, String path) {
	// Step 1. Get chaincode at m/44'/194'
	// EOS Coin type is defined at SLIP44 ref: https://github.com/satoshilabs/slips/blob/master/slip-0044.md
	// We believe that chaincode are more private
	MnemonicUtil.validateMnemonics(mnemonics);
	DeterministicSeed seed = new DeterministicSeed(mnemonics, null, "", 0L);
	DeterministicKeyChain keyChain = DeterministicKeyChain.builder().seed(seed).build();
	DeterministicKey parent = keyChain.getKeyByPath(BIP44Util.generatePath(path), true);

	# 你可以从该 URL 下载这个配置文件: http://surge.run/config-example/ios.conf
	# 用编辑器编辑后，再通过 iTunes, URL, AirDrop 或者 iCloud Drive 复制回 iOS 设备
	# Version 2.0

	[General]
	# 日志等级: warning, notify, info, verbose (默认值: notify)
	loglevel = notify
	# 跳过某个域名或者 IP 段，这些目标主机将不会由 Surge Proxy 处理。(在 macOS
	# 版本中，如果启用了 Set as System Proxy, 那么这些值会被写入到系统网络代理
	# 设置中.)