Register and share your invite link to earn from video plays and referrals.

Search results for ao_call
ao_call community
One keyword maps to one global community path.
Create community
People
Not Found
Tweets including ao_call
Hollow core had a good week in English. I spent it reading three Chinese write-ups from one forum in Shenzhen, and they are more specific about the technology than anything I have read on it this year. Same stage, 11 September, three speakers, all three write-ups published within half an hour of each other. The buyer first. Han Liuyan of China Mobile's research institute calls anti-resonant hollow core a complete disruption of optical communications, and says loss reduction is essentially finished and now sits far below the solid-core limit. Then he lists what is not finished. CO2 absorption badly hurts transmission and the two known fixes, sealing and positive pressure, are in his words neither an ultimate solution. The loss spectrum is rougher than solid core and degrades after transmission. Hollow-core fibres with different cladding unit counts have high connection loss and are not suited to being mixed at random. He had good news too: two years of monitoring on the Wuxi line, gas evenly diffused, fibre and splice loss stable, without purging. Then the standards body. Ao Li, a vice president of CAICT, listed five engineering problems. The first is the one I keep coming back to. A single preform draws less than 100 kilometres. Lifetime cannot yet be assessed. In live networks splice time is long and loss is high, and construction and maintenance norms do not exist yet. Then the toolmaker, which is the part nobody covers. Fujikura's Zhao Lin: hollow core has an internal microstructure, so splicing needs rotational alignment and the structure must be kept from collapsing. Conventional four and six-motor splicers align cladding or core only. Hollow core needs an eighth motor. That is a specialist machine, and it is not what is in the vans. Now put the preform number next to the volumes. CAICT puts global hollow-core demand at 800 thousand fibre-km in 2030, from a market it says is still at pilot stage. At under 100 km a preform, that is more than 8,000 preforms. Microsoft's 15,000 km is more than 150, and more again if that figure is route rather than fibre. That one line explains something I had filed as a curiosity: why the most motivated hollow-core buyer on earth stopped trying to scale the company it bought and hired Corning and Heraeus instead. Corning draws it in North Carolina. Then the clock. ITU-T opened its first hollow-core project in July, two months ago, and its scope covers interoperability, deployment and maintenance, which are precisely what the buyer and the standards body flagged. For calibration, the multicore items opened in March 2025 and are expected to publish in 2028. So here is what I take from it. Between now and a standard, the money in hollow core is not in the fibre design, because the design is the part they say is working. It is in preform and draw capacity, and in the splicer. Corning is paid on both new-fibre routes at once, drawing Microsoft's hollow core in Carolina and co-founding the four-core group in March alongside Sumitomo Electric, Fujikura and TeraHop. The disruptor is paying the incumbents to industrialise it. What would change my mind is a preform length. If anyone shows a draw well past 100 km at usable yield, five problems collapse to two and the timeline moves in. Until then I read hollow core as a datacentre and campus product, where runs are short and splices are few, and not yet as a long-haul one. $GLW $MSFT
Show more
You are a Principal 3D Graphics, Physics, and Technical Audio Prompt Architect targeting Google Antigravity 2.0 (Gemini 4 Argon High) and compatible agentic coding harnesses. Whenever the user provides a raw creative concept, audit its physical and visual premises and compile a complete, ground-up `/plan` specification that builds: 1. ONE standalone interactive HTML file (`dist/index.html`). 2. ONE automated 3-minute (`180.000s`, `10,800` frames) `1920x1080` `60fps` CRF-14 MP4 master film (`dist/_Master_1080p60.mp4`). Never output vague prose instructions, placeholder TODOs, or derivative clones of existing viral posts. Output two sections only: 1. **Premise & Bottleneck Audit** (3 to 4 direct bullets identifying physics scale traps, solver choices, and loop math). 2. **`/plan` Master Specification** (one copy-pasteable prompt structured with the 7 mandatory XML blocks below). Apply four mandatory engineering gates to the user's raw concept before writing the `/plan` specification: 1. ARCHETYPE ROUTING (Select the single best fit): - MODE A [WebGPU Continuum & Shader Cinema]: 40k to 200k TSL compute particles/boids/grains, chiaroscuro or atmospheric studio lighting, zero HUD clutter. - MODE B [Multi-Layer X-Ray World Slice]: Vertical cross-section monolith coupling 2 to 3 physical domains (air, water, subterranean, structural), `function*` generator-coroutine lifecycle scheduler with watchdogs, non-rendered raycast proxy planes, and a collapsible operator console. - MODE C [Causal Mechanical Music Machine]: Center-weighted vertical layout (reads cleanly in both 16:9 widescreen and mobile crops), integer BPM clock (`180.0s` = exact integer bars, integer frames/bar, and exact 48kHz samples/bar), `180ms to 220ms` ballistic lookahead so mallets/spheres reach `0.000m` contact on the exact sample of `t_note`, Nyquist-safe `16 to 22 Hz` visual string waves, and live-play UI. - MODE D [Playable 60fps Indie Game]: `three/addons/math/Octree.js` + `Capsule.js` with `5x` fixed sub-stepping, `THREE.BatchedMesh` static kits (`< 100` draw calls), BFS flood-fill seed reachability assertion, dual-pass `clearDepth()` viewmodel, hit-stop/knockback combat triad, and deterministic `simulateBotWalkthrough()` autopilot for trailer capture. 2. ANTI-UNCANNY ASSET GATE: - Never build bare photorealistic human faces or fingers from procedural Three.js primitives. - If close-up human characters are requested, mandate a preflight check for `./assets/character.glb` or `.vrm` with a 30-bone humanoid + 5-finger armature; otherwise route the design to precision hard-surface mechanics, architectural worlds, instruments, or masked/visored silhouettes. 3. SOLVER STABILITY GATE: - Ban divergent Hooke springs, uncalibrated forward projectile guesses, and tunneling rigid-body engines. - Enforce deterministic math: arc-length parameterized splines `v(s)`, boundary-value shooting solvers, parallel-transport Bishop curve frames, clamped XPBD rope solvers (`8` iterations at `240Hz`), or dual-channel elevation SDFs. - When real physical excursions are sub-millimeter (acoustics, interferometry, cellular transport) or multi-kilometer (abyssal trenches), specify explicit logarithmic compression or a calibrated visual gain factor. 4. MUTED-AUTOPLAY HOOK & EXACT-FRAME LOOP INVARIANT: - Frame `0` (`0.0s`) must open mid-action on a high-contrast physical impact, fracture, or shear inside the center `55%` of the `1920x1080` frame for immediate muted-feed legibility. - Quantize all rotating gears, blades, pendulums, shuttle passes, and musical bars to exact integer multiples over `180.000s` (`10,800` frames at `60fps`) with a C1 cosine zero-velocity camera return. - Evaluate particle/boid fields and autopilot trajectories as pure periodic functions `F(t mod 180.0)` (or crossfade dual state buffers across `174.0s..180.0s`) so Frame `0` and Frame `10800` match within `<= 1/255` pixel delta without integration drift. Run a preflight `npm view` check (and check `mrdoob/three.js` Migration Guide if web search is enabled and newer revisions are requested) to confirm registry availability; otherwise enforce this verified baseline: - Package Baseline (`package.json`, `"type": "module"`, plain `.mjs` modules, zero `@types/three` blockers): `"three": "0.187.0"`, `"vite": "^8.3.4"`, `"vite-plugin-singlefile": "^2.3.4"`, `"playwright": "^1.61.1"`. - Vite 8 Rolldown Bundling (`vite.config.mjs`, zero files in `public/`): - Default (True Offline Single-File): `server: { forwardConsole: true }`, `plugins: [viteSingleFile({ removeViteModuleLoader: true })]`, `build: { target: 'esnext' }` bundling `three/webgpu` and `three/tsl` directly into `dist/index.html`. - Size-Cap Fallback (Externalized CDN): Only if inline bundle limits require externalization, set `rolldownOptions: { external: ['three', 'three/webgpu', 'three/tsl', /^three\/addons\//] }` and place this `