A quick prototyping tool: why should AI be used when you can do it quickly :D

This document specifies a network-layer protocol, IPv7, that extends
the Internet Protocol model with an identity-carrying address form
and an origin-validation mechanism intended to mitigate abuse of
residential proxy infrastructure. IPv7 replaces purely numerical
source addressing with a hierarchical identity string and a Variable-
Length Identity Block (VLIB) that carries an Ephemeral Identity Token
(EIT), provider and tenant identifiers, role/policy signalling, and
an Origin Signature verifiable by the originating provider. The
protocol enables routers to apply policy and reputation signals at
the network layer while limiting disclosure of a subscriber's long-
term identity to intermediate systems. This document addresses
growing security challenges in Internet-connected devices (IoT),
including smart TVs, appliances, and other residential endpoints that
are vulnerable to residential proxy exploitation and botnet
infection.

How a player often play minecraft steps by steps

The post lists practices to improve user-experience of command-line interface.

Problematic patterns

1. Borders in TUIs should always be drawn with characters specifically intended for textual interfaces (e.g., boxdraw characters).
2. Borders should be used sparingly, as they end up causing issues when the window is re-sized
3. Decorative content in CLI output should be limited, since the output of CLI utilities can be piped through other programs.
4. Nearly all animated spinners are extremely problematic for screenreaders. A simple progress meter and/or numeric percentage combined with flags to enable/disable them is preferable.
5. Excessive animation and color can harm users with attention and/or vestibular disorders, and some on the autism spectrum. Tools should respect the NO_COLOR environment variable.

Accessibility

6. Does the tool is usable once sended in espeak-ng?
7. Have a look to the WCAG
8. Avoid ASCII-art
9. Keep it boring to other common utilities to reduce the learning curve.
10. Follow convention: POSIX-like options
11. Be predictable with the options. The command only do one thing well.

Documentation

12. Write man pages. If your utility has a config file with special syntax or vocabulary, write a dedicated man page for it in section 5 and mention it in a “SEE ALSO” section.
13. Ennsure whatis and apropos work as intended after installing your man pages.
14. Try adding shell completions for your program, so users can tab-complete options.
15. Use a well-understood -h. It helps to generate shell completions. See https://www.busybox.net/ as example

Miscellaneous

1. Delegate output wrapping or detect the number of columns and format output to fit
2. Be safe. Addd a --dry-run or equivalent option.
3. Disable the colors when the tool is not a TTY, or when the user explicitly enables them.
4. Check the binary name or the packages first. It can already be used. dnf can help.

Opinionated

1. --help should be blazingly fast as user can be stressed using it
2. Include example usage in the man page and accompanying documentation.
3. Send example usages to the tldr pages project if the tool gets popular.
4. Include an extended list of example command invocations and expected output. Make that document double as a test suite.
5. Make your man pages as similar to other man pages on the target OS as possible. Many programs parse man pages, and expect them to follow a predictable structure. w3mman handles hyperlinks; editer like vim support looking up man pages; Pandoc can convert man pages to a variety of different formats.
6. Conform to tools that share a similar niche. If you’re using Rust to make a fast alternative to popular coreutils. ripgrep or fd for Rust, go vet for Go are good examples.
7. Make the output readable to both humans and machines
8. Consider splitting related functionality between many executables (the UNIX way) or subcommands (like Git). See https://www.lucasfcosta.com/blog/ux-patterns-cli-tools#consistent-commands-trees for more
9. Don’t conflate CLIs and TUIs. A CLI should be non-interactive; a TUI should be interactive.

A script checking all NPM dependencies that have a commit from Claude AI in their 100 latest commits.

It will only ping the GitHub API thought. So dependencies hosted elsewhere won't work.

Generate anything related to security. It can't be used for serious project though.

Display a diagram of the automate created by the regex

Exactly similar to https://regexplained.com/

Explains the hashes visually

Lichen is the simplest possible CMS for the web that is friendly enough for non-technical users. Comprised of just a few Forth CGI scripts, it is extremely lightweight. This site is built in Lichen. It can also be used as a static site generator.

A voxel engine

We can use the oklch (OK L C H) and adjust the lightness and chroma from the hue, thus generating colors.

Creating colors from oklch is tedious, but they can derivated from other color codes from [#007ab8](./add-tag/007ab8) calc(l - 0.05) c h)

Tip: very light and very dark lightness levels have a tendency to look oversaturated.. a lot of color palettes look more cohesive when you reduce the chroma slightly as you move away from the middle-range of lightness towards the edges.

Example: https://codepen.io/cferdinandi/pen/zxoYpeL

This example is good for dynamic colors.

Pour naviguer et décoder des formats binaires

It provides a binary representation of the sign, exponent and mantissa

n8n

Following the basics of anchor positioning, there are many more use cases for this layout specification. Note this is not supported by browsers yet.

Logical properties can be used for the alignment.

position-try-fallbacks can be defined by the developer with @position-try. It accepts few rules: inset properties, margins, sizing, self-alignment, position-anchor, position-area.