v0.2.0:7 — align package copy with website positioning
The Start9 registry card was still showing "Keysat — self-hosted Bitcoin-paid software license server" while keysat.xyz now leads with "Bitcoin-native self-hosted licensing service for software creators." Operators landing on the registry from the marketing site got a jarring tagline mismatch. Aligned everywhere the old copy was hardcoded: - startos/manifest/i18n.ts (short + long descriptions — these drive the registry card) - assets/ABOUT.md (in-StartOS About panel) - README.md (root + licensing-service/) - licensing-service/Cargo.toml description Long description also picked up two updates that should have landed when the features did but never made it into the marketing copy: - Zaprite mention (Bitcoin + cards) alongside BTCPay - Recurring subscriptions + in-place tier upgrades Pure copy change. No code, no behavior, no schema. Republishing as :7 because the registry card text lives inside the .s9pk and won't refresh on operators' boxes without a version bump.
This commit is contained in:
@@ -2,15 +2,17 @@
|
||||
// later. Only English is filled in here; add more locales as needed.
|
||||
|
||||
export const short = {
|
||||
en_US: 'Keysat — self-hosted Bitcoin-paid software license server.',
|
||||
en_US: 'Bitcoin-native self-hosted licensing service for software creators.',
|
||||
}
|
||||
|
||||
export const long = {
|
||||
en_US: `Keysat lets you sell licenses to your own software products using
|
||||
Bitcoin payments via BTCPay Server. Every instance runs on the operator's own
|
||||
StartOS — there is no central authority. The service issues Ed25519-signed
|
||||
license keys that downstream software can verify offline, with optional
|
||||
expiry, entitlements, fingerprint binding, and per-seat activation caps.
|
||||
Supports multiple products per instance and closed-source, open-core, and
|
||||
en_US: `Keysat is a Bitcoin-native, self-hosted licensing service for
|
||||
software creators. Sell licenses to your own software products with payments
|
||||
via BTCPay Server (Bitcoin / Lightning) or Zaprite (Bitcoin + cards). Every
|
||||
instance runs on the operator's own StartOS — there is no central authority.
|
||||
The service issues Ed25519-signed license keys that downstream software can
|
||||
verify offline, with optional expiry, entitlements, fingerprint binding, and
|
||||
per-seat activation caps. Supports multiple products per instance, recurring
|
||||
subscriptions, in-place tier upgrades, and closed-source, open-core, and
|
||||
open-source distribution models.`,
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user