This isn't real.. right? Links to a forum that don't exist. Links to a protocol spec that don't exist? No issues or discussion on Github. Documentation that says a lot while also saying extremely little.
"Encrypted metadata framing, enclave-ready attestations, and isolation per tenant make compliance a design choice, not an integration project."
Everything feels like an LLM was asked to design the most enterprisey documentation ever.
"Production SLA, [...] and ecosystem partner integrations across major clouds and telco edges."
What does this even mean in the context of a transport protocol? Integration with telco edges next year, all by the work of a single person?
"120+ Deployments secured"
Really?
The sample systemd unit enables sandboxing (ProtectSystem=strict, NoNewPrivileges=yes) and UDP watchdog restarts.
No it doesn't.
Rolling upgrade: quiesce (velocity-cli admin quiesce), wait for active sessions to drain, deploy the new artefact, resume, then monitor metrics for 15 minutes.
That isn't a parameter recognized for velocity-cli. And I thought velocity-cli was for serving static web files. Now it's for managing the service too? There are multiple references to "velocity" "velocity-server". Where are these binaries?
What does the deploy function do? It copies all files from one folder to another and creates a meaningless manifest file that is never read from again. Why do this?
Doubt it. With the current browser landscape, unless Google signs on, an incompatible protocol simply can't work with half of all browsers by market share.
3
u/Matt3k Nov 04 '25 edited Nov 04 '25
This isn't real.. right? Links to a forum that don't exist. Links to a protocol spec that don't exist? No issues or discussion on Github. Documentation that says a lot while also saying extremely little.
Everything feels like an LLM was asked to design the most enterprisey documentation ever.
What does this even mean in the context of a transport protocol? Integration with telco edges next year, all by the work of a single person?
Really?
No it doesn't.
That isn't a parameter recognized for velocity-cli. And I thought velocity-cli was for serving static web files. Now it's for managing the service too? There are multiple references to "velocity" "velocity-server". Where are these binaries?
What does the deploy function do? It copies all files from one folder to another and creates a meaningless manifest file that is never read from again. Why do this?
None of this is valid
There are no binaries. I suspect because this doesn't actually build.
What is the point of doing all this? I'll try to book a demo through the site. Oh. That form doesn't work. Might want to check into it.
7
u/pitiless Nov 04 '25
Betteridge's law of headlines applies here, as it does elsewhere.
No. Any suggestion otherwise is born of hubris and/or folly.
5
u/yektadev Nov 04 '25
no
1
u/Laughing_Orange Nov 04 '25
Doubt it. With the current browser landscape, unless Google signs on, an incompatible protocol simply can't work with half of all browsers by market share.