Wikenigma is a unique wiki-based resource specifically dedicated to documenting fundamental gaps in human knowledge.

Reveal domains parked at the same IP as a given domain. It can also show IPs (and their domains) nearby.

A nice series of articles explaining the internals of Linux resources - files, pipes, processes, sessions and terminals (tty), from the perspective of a SRE engineer.

Generate unique tokens that notifies a webhook or an email address when accessed. Many tokens are supported, including DNS, URL, document, binary, etc. (Sort of like tracking pixel on websites but with a lot of other types of triggers)

5GHz band overlaps with some radar installation. Some channels are required to perform a mechanism called Dynamic Frequency Selection (DFS) to adjust the frequency to avoid colliding with radar signals. DFS can cause a slow down in the start up time and may disrupt normal usage intermittently.

To mitigate DFS events, you can pick channels that are not subjected to DFS scan. You can check out this page for information of DFS channels on different countries: https://en.wikipedia.org/wiki/List_of_WLAN_channels

A collection of seemingly interesting data structure and algorithms.

Check IP leakage through your BitTorrent client. The page generates a magnet link. Try download it with your BitTorrent Client, and your IP will be revealed on the webpage.

Also check out: https://ipleak.net.

How different bitrate mode works for video encoding and which one should you choose?

In short, CRF should be good enough for most non-streaming use because it doesn't waste bits on easy to compress clips (quality based). Otherwise use a Capped-CRF if a maximum bitrate cap if necessary.

I'm deeply moved by this article. I can't say how much I do feel the same way about ongoing decadent of humanity. The world has been more material than ever, and yet the people are a lot less alive nowadays.

No "outsourced" TL;DR for this article. You should to read it on your own.

This article explained the concept pretty well! It not only showed how to use Flexbox, but also the reason it's designed this way. Here are a few things I learned:

• the default css layout algorithm is flow. flexbox and grid are two completely different layout. by using display: flex we are switching layout algorithm.
• justify means to position along primary axis, whereas align means to position along cross axis (think of a kebab skew vs cocktail wiener)
• content is a group of things that can be distributed, whereas items refers to single items that are positioned individually.
• width in flow layout is a hard constraint, whereas in flexbox layout it's a "hypothetical size", meaning only the hinted size.
• flex-basis is just like the width (or height) attribute along the primary axis. A difference is that flex-basis cannot reduce an item below its minimum size.
• flex-grow: n to use the remaining n_i/(sum n_i) of space; specially, flex-grow: 0 stick to its intrinsic size.
• flex-grow is used when the children's size combined is smaller than the size of container, whereas flex-shrink is used when children's size is bigger.
• flex-shrink: n shrinks the children by making each pay the debt in size. each pays a portion of (n_i/sum n_i); specially flex-shrink: 0 makes the child never shrink.
• flexbox layout never shrinks an item below its min-width (or height), regardless of their flex-shrink value, and even at the cost of overflowing the container.
• gap is a convenient attribute comparing to setting margin because it doesn't add spacing on the ends.
• margin: auto is an useful alternative to flex-grow: 1 because it gobbles up the spare space without changing the item's size.
• with flex-wrap: wrap, items won't shrink below their hypothetical size, and overflowed items wrap to a new row/column.
• when flex-wrap: wrap takes effect, we use align-content to adjust the position of all items about the cross-axis.

IoT circuit drawing and simulation. Supports many real parts.

A comprehensive introduction to the working and graphics pipeline.

A webgl demo scene (?) of infinitely recursive game of life in game of life.

An linux sandboxing tool with pledge() syntax by Justine Tunney, author of "actually portable executable" and "redbean".

Alternative to apparmor (kernel module) or bubblewrap (cgroup/namespace).

it's intended to dispel a few common myths and help regular people understand UEFI a bit better.

The article is a bit long, but it indeed contains a lot of information I actually wanted to know.

A theory on how ChatGPT find it so hard to calculate the rot13 cipher - ChatGPT is only capable of System 1 thinking, which is based on quick intuition, whereas the rot13 problem requires going through elaborated inference, which requires the System 2 thinking ability.

Make a fragment shader with a node editor. You connect the nodes, preview the effect, and get a shader definition.

This project is similar to something I wanted to create for a long time.

An advocate on using Postgres to replace the role for cache, data warehouse, message queue, document database, full-text search, and backend API. It surprises me that Postgres has all these capabilities.

A thought provoking article on the coding syntax of sequences (lists, fields, pipes). An interesting reflection on how we typically intuit about sequence syntax in natural languages and how it may be better written in the other way around.

A bunch of trivia about linking in UNIX-like operating systems.