Hacker News new | past | comments | ask | show | jobs | submit login

It comes down to the problem statement and what the constraints are. This is solving for using the phone-only scenario, which is perfectly valid.

If you want to address a phone-with-internet-backchannel, that's valid too - but it assumes different problem statement and constraints.






Please pay more attention to the point 3 in my original post. To reiterate: their encoding is hilariously bad, and is easily outcompeted by a modem from the 60s.

youre missing the forest for the trees. the library this demo is using for audio encoding (ggwave) was not made by the creators of this demo. speed (or lack thereof) aside, having a direct audio<->text encoding is much more computationally efficient than speech<->text generation.

on the subject of the encoding efficiency, the ggwave depo mentions the use of reed-solomon error correction to make transmission more reliable. im struggling to find any info on error correction used by bell 103 or other modems, but if they aren't as robust that could partially explain the discrepancy you're describing


Sounds more futuristic than old dial-up sounds though

I think the most important part is the bitrate. As you said elsewhere: "time is money". Seems like you're not saving that much money



Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: