Skip to content

Commit 95ca05a

Browse files
codekilncodekiln
committed
fnox vs secretspec
1 parent 23e932c commit 95ca05a

4 files changed

Lines changed: 18 additions & 7 deletions

File tree

‎journals/2026_04_23.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
- [exe.dev](https://exe.dev/docs/what-is-exe) - see blog post [crawshaw - 2026-04-22](https://crawshaw.io/blog/building-a-cloud) - this is a bespoke micro neocloud provider made by an individual.
22
- interesting discussions
33
- of [[NixOS]] integration with [[secretspec]] [NixOS integration · Issue #65 · cachix/secretspec](https://github.com/cachix/secretspec/issues/65)
4-
- of [[mise]] creator's new [[secretspec]]-type project that integrates with mise, [Mention fnox · Issue #42 · cachix/secretspec](https://github.com/cachix/secretspec/issues/42) - derailed into [[AI/Anti]] rant
5-
- [[@jdx]]
4+
- of [[mise]] creator [[@jdx]]'s new [[secretspec]]-type project that integrates with mise, [[fnox]] - [Mention fnox · Issue #42 · cachix/secretspec](https://github.com/cachix/secretspec/issues/42) - derailed into [[AI/Anti]] rant
5+
- see also [[fnox/vs/secretspec]]
66
- ## with [[Adobe]], the simplest things are the hardest
77
- This morning I wanted to a lightweight edits of a movie file that was in [[Lightroom/Classic]]. I just needed to edit the start and end times and add some text.
88
- Discovered that [[Adobe/Rush]] was discontinued (technically, it will no longer be available in September). Apparently Adobe no longer has a lightweight, desktop-native video editor; the closest thing is [[Adobe/Premiere/Pro]], which is, needless to say, overkill for this use case.

‎journals/2026_04_24.md‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,7 @@
55
- [[Learning/Idea/26/03/Terminal toolbelt learning]]
66
- [[OpenAI/Codex/CLI]] renamed from `OpenAI/GitHub/codex`
77
- ### [[Filed]]
8+
- [[Google/AI/Edge/Eloquent]]
89
- [[Interop/Adversarial]] created with [[Person/Cory Doctorow]] definitions and verified EFF Deeplinks citations (2019 interoperability series)
910
- [[Lazygit/26/04/24 Fri Issues with git merge conflict resolution]]
1011
- [[Lazygit/Keyshort/Show Reflog]]
@@ -13,4 +14,4 @@
1314
- [[git/reflog]]
1415
- [[git/show]]
1516
- [[OpenAI/Codex/CLI/Q/Is there a way to export a transcript of a conversation to a file?]]
16-
- [[pbcopy]]
17+
- [[pbcopy]]

‎pages/GitHub___Issue.md‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
alias:: [[GitHub Issues]]
2+
tags:: [[Project Management]]
3+
4+
- # GitHub Issues
5+
- By default each [[GitHub/Repo]] comes with an Issues tab where the public can post issues.
6+
- Typically, each [[PR]] closes at least one github issue.

‎pages/fnox___vs___secretspec.md‎

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,10 @@
1-
- Purpose of this page
2-
- Highlight **capabilities that show up in one tool’s public story but not the other’s**, so you can scan for gaps instead of reading two parallel product pitches. Provider catalogs change; treat bullets as **“documented on the official site when this note was written”**, then verify in each project’s current docs. [^1] [^2]
3-
- ## Features emphasized for **fnox** but not for **[[secretspec]]**
1+
# [[fnox]] vs [[secretspec]]
2+
- An attempt to highlight **capabilities that show up in one tool’s public story but not the other’s**.
3+
- [[My Notes]]
4+
- [[My Thoughts]] [[2026-04-24 Fri]]
5+
- think that [[@jdx]] took a look at secretspec's blog post [[devenv/Blog/25/07/Announcing SecretSpec]] and said "this seems too perfectionistic" and "i could do better than that" w.r.t. how [[secretspec]] thinks that using tools like [[sops]] and `age` to encrypt [[Secrets]] in a [[git/repo]] repo is not a good idea, while [[@jdx]] included that as a core featureset in [[fnox]].
6+
- in general, [[fnox]] seems like it has more integrations and is moving faster, but it doesn't have a [[GitHub Issues]] tab, which is the first time I've ever seen that. this decision reminds me of when youtube videos and blog posts have comments disabled. basically, he's offering his own solution for himself to the public, but not asking for contributions. part of me reticulates a bit at that thought; how will he catch all the bugs? but then again, this makes me think about how [[nvim/treesitter]]'s creator recently archived the project because the [[Open Source]] community was just nasty to him. If this is his way of making his personally useful stuff public while staying sane, ... that seems fine to me!
7+
- ## Features emphasized for [[fnox]] but not for **[[secretspec]]**
48
- **Encrypt-to-git in the project file**
59
- **fnox** documents storing **encrypted ciphertext** (or KMS-style encrypted payloads) **inside `fnox.toml`** that you commit—for example via **age** (including SSH-key flows) or **AWS / Azure / GCP KMS**—so teammates clone **values-in-repo** without plaintext in history. [^1]
610
- **[[secretspec]]**’s public positioning is the opposite: **`secretspec.toml` declares requirements only**; it should **not** carry real secret material, even encrypted—the committed file is the **contract**, not the vault. [^2]
@@ -44,4 +48,4 @@
4448
- [[Person/Jeff Dickey/GitHub/fnox]] — canonical repo link
4549
- ## Footnotes
4650
- [^1]: https://fnox.jdx.dev/
47-
- [^2]: https://secretspec.dev/
51+
- [^2]: https://secretspec.dev/

0 commit comments

Comments
 (0)