IceCodeNew IceCodeNew

AI Writing Tropes to Avoid

Add this file to your AI assistant's system prompt or context to help it avoid common AI writing patterns. Source: tropes.fyi by ossama.is

Word Choice

"Quietly" and Other Magic Adverbs

Friendly Python

本文基于 Frost Ming “friendly python” 标签下的文章，整理出偏向工程实践的开发范式、规范与典型好/坏代码范式示例。重点是“对使用者友好 + 对维护者友好”，并强调在 Python 中利用语言特性与生态扩展点进行合理抽象。

资料来源

Convert SSH config to Ananta hosts csv.

positional arguments:
  csvfile      Path to the Ananta hosts csv.

optional arguments:
  --ssh SSH    SSH config file. (default: ~/.ssh/config)
  --user USER  default ssh user

🤗Huggingface Model Downloader

Note

(2026-06-18) Add 📊Download Progress, 🔁integrity-aware resume (re-fetch missing or changed files), and fast, resumable listing for 📚repos with massive file counts.
(2025-01-08) Add feature for 🏷️Tag(Revision) Selection, contributed by @Bamboo-D.
(2024-12-17) Add feature for ⚡Quick Startup and ⏭️Fast Resume, enabling skipping of downloaded files, while removing the git clone dependency to accelerate file list retrieval.

Considering the lack of multi-threaded download support in the official huggingface-cli, and the inadequate error handling in hf_transfer, This command-line tool leverages curl and aria2c for fast and robust downloading of models and datasets.

Features

Web Service Fronting

Multiple Web properties on a single IP address

Hosting multiple websites on a single public IP address on the standard HTTP(S) ports is relatively easy with popular web servers like Apache, Nginx and lighttpd all supporting Virtual Hosts.
For Web Services which bundle their own HTTP server, things get more complicated, unless their HTTP stack can be shared somehow. More often than not, the application's HTTP stack listens directly on a dedicated TCP port.

Hosting multiple services on a single IP then requires using a fronting server listening on the standard HTTP port, and routing to the right backend service based on the host name or the path sent by the client.
Path based routing is cumbersome, usually requiring either the service to be aware of the path prefix, or a rewrite by the HTTP fronting server of all absolute URLs in the requests and responses.
Hostname based routing is more straightforward. The fronting server can just look at the [HTTP/1.1 Host header](https://tools

	const https = require("https");

	const token = ""; // change this to you telegram bot token!
	const chatId = ""; // change this to your telegram chat id!
	const cookie = ""; // change this to your shanbay cookie!

	const PATH_API = (page) =>
	`/wordsapp/user_material_books/blozps/learning/words/today_learning_items?ipp=10&page=${page}&type_of=NEW`;

	const options = {

	addEventListener('fetch', event => event.respondWith(handleRequest(event.request)));

	// Add environment variable `TGBOT_TOKEN` via Worker-Settings
	async function requestTelegramBotAPI(method, payload) {
	return fetch(`https://api.telegram.org/bot${TGBOT_TOKEN}/${method}`, {
	method: "POST",
	headers: {
	"Content-Type": "application/json; charset=utf-8"
	},
	body: !payload ? undefined : JSON.stringify(payload)

	# K4YT3X Server/Community Zsh Configuration
	# Copyright 2017-2026 K4YT3X.
	# Created: December 16, 2019
	# Updated: January 27, 2026

	# This program is free software: you can redistribute it and/or modify
	# it under the terms of the GNU General Public License as published by
	# the Free Software Foundation, either version 3 of the License, or
	# (at your option) any later version.
	#

	#
	# This is the ultimate HAProxy 2.0 "Getting Started" config
	# It demonstrates many of the features available which are now available
	# While you may not need all of these things, this can serve
	# as a reference for your own configurations.
	#
	# Have questions? Check out our community Slack:
	# https://slack.haproxy.org/
	#