giles
4f02f82f4e
Parser: skip unit suffix when next ident is a comparison keyword (starts, ends, contains, matches, is, does, in, precedes, follows). Fixes "123 starts with '12'" returning "123starts" instead of true. eval-hs: use hs-compile directly instead of hs-to-sx-from-source with "return " prefix, which was causing the parser to consume the comparison as a string suffix. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
17 lines
1.4 KiB
Plaintext
17 lines
1.4 KiB
Plaintext
(defcomp ()
|
|
(~docs/page :title "Future Possibilities"
|
|
(~docs/note
|
|
(p "This page is speculative. Nothing here is implemented. It documents ideas that may or may not happen."))
|
|
(~docs/section :title "Custom protocol schemes" :id "schemes"
|
|
(p (~tw :tokens "text-stone-600")
|
|
"sx:// and sxs:// as custom URI schemes for content addressing or deep linking. An sx:// URI could resolve to an sx expression from a federated registry. This is technically feasible but practically unnecessary for a single-site deployment."))
|
|
(~docs/section :title "Sx as AP serialization" :id "ap-sx"
|
|
(p (~tw :tokens "text-stone-600")
|
|
"ActivityPub objects could be serialized as s-expressions instead of JSON-LD. S-expressions are more compact and easier to parse. The practical barrier: the entire AP ecosystem expects JSON-LD."))
|
|
(~docs/section :title "Sx-native federation" :id "federation"
|
|
(p (~tw :tokens "text-stone-600")
|
|
"Federated services could exchange sx fragments directly — render a remote user's profile card by fetching its sx source from their server. This requires trust and standardization that doesn't exist yet."))
|
|
(~docs/section :title "Realistic assessment" :id "realistic"
|
|
(p (~tw :tokens "text-stone-600")
|
|
"The most likely near-term improvement is sx:// deep linking for client-side component resolution. Everything else requires ecosystem adoption that one project can't drive alone."))))
|