Replace generic ideas with concrete Nix-flavored prompts

Mix of specific buildable projects (mesh store cache, NixOS home
server appliance, declarative personal cloud) and provocative
what-if questions (binary provenance verification, phone OS
attestation, system drift detection).

Author: zimbatm

site/index.html

@@ -169,19 +169,42 @@ <h2>Judging</h2>
       <section id="ideas">
         <h2>Ideas to get you started</h2>
         <ul class="ideas-list">
-          <li>P2P package distribution</li>
-          <li>Personal cloud on your own hardware</li>
-          <li>Decentralized identity / auth</li>
-          <li>Reproducible build verification</li>
-          <li>Local-first collaboration tools</li>
-          <li>Self-hosted alternative to a SaaS product</li>
-          <li>Transparent firmware / hardware audit</li>
-          <li>Encrypted backup with user-held keys</li>
+          <li>
+            A NixOS appliance your parents could run as their home server
+          </li>
+          <li>
+            What if <code>nix build</code> could prove a binary matches its
+            source&mdash;and a non-developer could verify it?
+          </li>
+          <li>
+            A mesh cache that shares Nix store paths over the local network at
+            a conference
+          </li>
+          <li>
+            <code>nixos-rebuild</code> but it deploys to a VPS you actually own,
+            with one command
+          </li>
+          <li>
+            What if your phone could cryptographically attest that its OS was
+            built from a public config?
+          </li>
+          <li>
+            A declarative personal cloud: email, files, calendar, contacts,
+            all defined in one flake
+          </li>
+          <li>
+            Peer-to-peer secret sharing for teams&mdash;no third-party vault
+            service
+          </li>
+          <li>
+            A tool that diffs what your NixOS system is <em>supposed</em> to
+            run vs. what it <em>actually</em> runs
+          </li>
         </ul>
         <p class="spaced muted">
-          These are starting points, not limits. The key question:
-          <em>would an average user benefit from this?</em> Sovereignty means
-          nothing if only experts can use it.
+          These are sparks, not boundaries. Build whatever you want. The only
+          test: <em>does it give a real person more control over their own
+          computing?</em>
         </p>
       </section>
 

site/style.css

@@ -200,6 +200,15 @@ td a {
     "Courier New", monospace;
 }
 
+/* Inline code */
+
+code {
+  font-family: "SF Mono", "Fira Code", "Fira Mono", "Roboto Mono",
+    "Courier New", monospace;
+  font-size: 0.9em;
+  color: var(--accent);
+}
+
 /* Ideas list */
 
 .ideas-list {