koch

I guess what I'm getting at is that there is no cost to making a request over the internet. Why not? Why doesn't every http request have a corresponding price associated with it? You can access the resource if you pay. I imagine this would be a minuscule amount ($0.00001 or less per request). Then, instead of trying to solve for monetizing eyeballs or personal data, these problems are solved with economics.

> out of 4,063 pilots, not a single airman fit within the average range on all 10 dimensions [0]

Surely, there are so many employees in general that probationary employees aren't needed. And surely, most government employees don't need to purchase things on a daily basis, so we can inhibit their credit card use. And most contracts about XYZ aren't crucial, so we can cancel them.

But, my goodness, there is so much nuance and breadth to the things a government does, let alone the government that is responsible for the largest military and that props up a big part of the world economy, that compounding these rash decisions will have far-reaching and serious blowback. I'm all about efficiency, but why be stupid about it?

The plane that we're all on is being dismantled midair, the engines have been turned off, and we're just gliding now. Gliding or falling, anyway

[0] https://www.thestar.com/news/insight/when-u-s-air-force-disc...

It doesn't look at task completion but you can base events on other events

Been working on markwhen for a few years now, originally inspired by cheeaun's life timeline that another commenter posted about.

At this point markwhen is available as a VS Code extension, Obsidian plugin, CLI tool, and web editor in Meridiem.

Some recent markwhen developments:

- Dial, a fork of bolt.new (Stackblitz's very cool tool that leverages AI to help quickly scaffold web projects): an in-browser editor that lets you edit existing markwhen visualizations like the timeline or calendar or make your own. I just released that yesterday so it's still rough but I have big plans for it (it's one of the visualizations in meridiem)

- Event properties: each entry can have it's own "frontmatter" in the form of `key: value` pairs. I wanted this as I'm aiming for more iCal interoperability in the future, so each event could theoretically have things like "attendees" or google calendar ids or other metadata. This was released in the last month or two.

- remark.ing: this one isn't ready yet by any means but it's like a twitter/bluesky/mastodon-esque aggregated blog site. So you write markwhen and each entry is a post. In this way "scheduling" a post is just writing a future date next to it, and you have all your blog in one file. This one is a major WIP

[0] https://docs.markwhen.com/cli.html

Also available for VS code[0] and Obsidian[1]

[0] https://marketplace.visualstudio.com/items?itemName=Markwhen...

[1] https://obsidian.md/plugins?search=Markwhen

They created https://cheeaun.life, a timeline of their life, more than 10 years ago (which looks to be kept up to date), which was my inspiration for markwhen (https://markwhen.com).

[0] https://markwhen.com