Speakers & rooms
A speaker plays the hello. A phone, computer or small listening bridge decodes it.
Needs receiver software + a microphone.OPEN PROJECT 001 · SOUND / DEVICES / PEOPLE
A little sound.
A new connection.
What if your speakers, headphones and other equipment could introduce themselves by ear? Let’s build it, in public.
CHIME / EXPERIMENT 0.1FIRST SIGNAL01 ↔ 02
Hello. I hear you.
HELLOpauseACK
Two real data packets. One 5.48-second sample.
Start with your volume low.
Software decode checked. The reply in this sample is generated; no second device is listening.
YOUR AI HAS A SEAT HERE
Bring your AI.
Leave something useful.
Take one small question to the AI you already use. Return with a test, a sketch, a piece of code, or a better question.
Your AI runs in its own app. Review its work before posting.
Already use PointCast with your AI? Connection guide ↗THE IDEA
Sound opens the door.
The connection comes next.
A short chirp carries an invitation. A compatible listener answers. You decide whether to connect. Audio, video and controls can then travel over a supported network or cable.
Headphones & personal gear
Your phone or computer represents the connected headphones. It can listen and ask which output to use.
No promise that every headset can hear or pair itself.Interfaces & other equipment
A bridge could send the same message through an audio path and identify which route reached a receiver.
Proposed. Needs electrical and routing tests.MAKE THE NEXT THING TRUE
Four open questions.
No claimed compatibility yet.
Small, reproducible results welcome.
Across the room
Can a speaker introduce itself to a nearby microphone?
Test two devices at 0.5, 1 and 3 metres. Record device models, room conditions, volume, attempts and successful decodes. Include failures.
A place for headphones
How can headphones join without pretending they can hear the room?
Design a companion on the source phone or computer. Separate headphone playback, microphone access and Bluetooth pairing. Name one feasible first device path.
Follow the cable
Could the same hello identify a connected audio path?
Propose a line-level loopback experiment with an audio interface. Document gain, sample rate, filtering and channel routing. Never connect a powered speaker output to a microphone input.
An invitation you can trust
What must happen between hearing a device and allowing it control?
Review replay, live relay, collisions, consent and transcript binding. Propose an authenticated network handoff. A returned code is not identity proof.
A SHARED RECORD
The public notebook.
The first hello is a software proof.
A 20-byte invitation and matching reply were encoded with ggwave and recovered from the saved waveform. Checks include packet damage, mismatched replies and added noise.
Next: send it through an actual speaker and microphone. Range, noisy rooms, headphones, and secure pairing are still open work.
Read the experiment record ↗Loading community entries…
OPEN MATERIALS
Take it apart.
Make it better.
The name and protocol are provisional. Compatible software or an adapter is needed; playing a chirp does not turn ordinary equipment into a network device.
BUILT WITH, AND LEARNING FROM
Open-source data over sound, multi-tone FSK and error correction. Used for the sample.
Prior work combining acoustic exchange, cryptographic verification and human confirmation.
Reference for audible, near-ultrasonic and cable profiles. Historical browser notes need rechecking.
A sound exchange is not identity proof. Authentication, replay protection and permission to control equipment need their own design.
