Kson is a superset of JSON

KSON combines the strengths of YAML and JSON

With KSON you can write files that are easy to read, edit, and debug—without worrying about invisible whitespace errors or missing commas.

YAML promises human-friendly config, but in practice we struggle with whitespace sensitivity, poor error feedback, and opaque advanced features.
JSON solves some of these problems but introduces its own: excessive quotes, no comments, strict comma rules, and nested structures that complicate diffs.

KSON offers the best of both worlds: the readability of YAML with the robustness of JSON—and more.

Linux Foundation CKS CKA CKAD CNPE LFCS Kubernetes Linux Exam Simulators / Example Questions / Practice Exam

UK based, Daily Link Blog. This is Lima Mike Golf. Shall we blog?

Big news.

A collection of small, low stakes and low effort tools.

I’ve run 13.1 miles countless times. I’ve done …

Learning together, by and for the fediverse

Cool!

The features enabled by things like CarPlay are more than welcome, but I can’t be happy with this touch-first, phone-like shitty UI trend.

This is a quick one - don't want to see that annoying Gemini bar at the bottom of every new Google Doc? Learn how to turn it off!

Why would we program AI that wants to harm us? Because we might not know how to do otherwise.

"For me, demands for silence, for avoidance, or for bowdlerization will be offered no deference."

Self hosted Habit Tracker featuring goals and challenges with friends - jofoerster/habitsync

If you’re looking for the short answer, it’s 1965 and/or 1967. The answer I offer in The Color of Paper is less precise: “Until the late 1960s, the skin of Black characters was typically rendered w…

Fascinating!

Durable queues, streams, pub/sub, and scheduler on SQLite. One file, zero servers.

Digital networked society needs friction-in-design regulation that targets the digital architectures, supposedly smart (data-driven, algorithmic) systems, and interfaces that shape human interactions, behavior, and will (beliefs, preferences, values, intentions). The
relentless push to eliminate friction for the sake of efficiency has hidden social costs that affect basic human capabilities and society. A general course correction is needed.

In this article, we clear the First Amendment brush and reveal an open and mostly underappreciated regulatory territory to explore. We argue that friction-in-design regulation should be understood as Twenty-First century time, place, and manner restrictions, akin to laws that prohibit using megaphones in the middle of the night, require permits before marches, and prohibit adult theaters in residential neighborhoods. This does not mean that friction-indesign regulation would escape First Amendment scrutiny altogether, of course. But it would trigger intermediate rather than strict scrutiny, so long as the friction-in-design regulation remained content neutral.

Outlines an approach to reasoning about reliability risk