feat: update site content and contact experience - #23
Open
schnuartz-ai wants to merge 3 commits into
Open
Conversation
Support group members kept asking where to verify the release signing key. Update it site-wide and make the certification chain explicit and independently checkable instead of pointing at a single vague source: - Fix the stale "Specter Signer" name/fingerprint (785A...) and the broken "here here" text, replacing with "Specter Signer 2026" / 9DC3 3CA8 3058 9DE3 B322 5C26 EEF5 756B 2EA4 2349 everywhere. - State plainly that the release key is certified by Kim Neunert's (@k9ert) personal key, with that key's own fingerprint, and link to three independent ways to verify his identity: GitHub's GPG key API, Keybase (which also cross-links his GitHub/X), and the Ubuntu keyserver. - Extract the previously triplicated (Mac/Windows/Linux) key-info block into one shared component so future key rotations only need updating in one place - that duplication is exactly how the old typo and stale fingerprint went unnoticed on 2 of 3 tabs.
…te, hardcoded year Cross-checked against the v2.1.10 GitHub release notes: - Docker images moved to GHCR; the old Chiang Mai LN devs images were only used before v2.1.2 and were still presented as the only option. - The macOS build isn't notarized, so Gatekeeper blocks it on first launch; add the documented `xattr -cr` workaround. - The Imprint page had its own hardcoded "© 2024" in the body content, separate from the site-wide footer (which already uses the current year) - missed in the earlier footer fix since it's a second, independent copy of the copyright line.
✅ Deploy Preview for specter-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Verification