A developer-focused guide to EOA wallet signature verification, covering secp256k1, ECDSA r/s/v signatures, public key recovery, keccak-256 address derivation, and how SIWE proves wallet ownership without exposing the private key.
This article explores how, against the backdrop of rapid AI development, the cost of using advanced models will become a key factor in a new round of social screening. The author expresses concern that rising model usage fees may lead to a digital divide, pointing out that when usage costs increase from today’s subsidized prices to higher levels, ordinary users may struggle to afford them, resulting in class-based differentiation in technology access. The article also reviews AI’s diverse applications in fields such as security, video, and music, emphasizing that AI is expanding from a coding tool into broader industries. From a personal perspective, the author describes how to navigate the tide of the times with limited capital and calls for attention to the impact of technology costs on public access. Keywords: AI model costs, digital divide, technological screening, AI applications, anxiety of the times.
Realizing I’ve been suppressing my emotions, reflecting on how past living habits have led to fear of the outside world and inner stillness. Hoping to find my true self through interacting with the world, while facing the sense of responsibility in choosing a direction and the fear of losing other possibilities. The true self needs to be shaped through exploration, and choosing a future direction means giving up other possibilities.
A record of the migration from NotionNext to Mizuki, mainly due to NotionNext's limitations. Mizuki was chosen for its lightweight nature and good balance of features, supporting diaries and project showcases. The configuration process is simple, with content controlled via md and ts files, and it also connects to the Bangumi API. The plan is to synchronize Notion content via CI, implement multilingual support, and address the issue of image links expiring.
Developing a VSCode extension requires preparing Node.js, VSCode, Yeoman, and generator-code. Yeoman can be used to generate the basic plugin structure and understand key files such as package.json and the entry file src/extension.ts. The plugin can be run and tested through the debug panel, and after completion it can be packaged with vsce and published to the VSCode Marketplace. Plugin activation is defined through activationEvents in package.json, supporting multiple types of activation events.
Get latest website content in time without manually visiting
Manage subscriptions to multiple websites in one place
Avoid missing important updates and articles
Enjoy an ad-free, clean reading experience
It is recommended to use Feedly, Inoreader or other RSS readers to subscribe to this site.