ejb503
There is an over indexing on mental capacity, and an underappreciation for grinding and actual, erm, hard work and understanding…
I see this a lot with learning a foreign language. Intelligent people assume it will be simple for them, because they are intelligent. Spoiler, actually less intelligent folk tend to have less ego, ergo they progress much faster (personal experience, not gospel).
I don’t really care about AGI. I care about how good you are at your job. And the fact of the matter is, Gen AI isn’t that good at all.
Generative AI is misunderstood as a sentient tool that is highly intelligent and thus capable of expert output. Truth is, Generative AI is capable of performing enormous amounts of work to an intermediate level.
Given the speed of the output, we forgive Generative AI for errors and inaccuracies that we wouldn’t begin to tolerate in any walk of life, i.e. from absolutely anybody who actually knew what they were doing. "Sorry sir, it wasn't the correct arm I amputated, but it was still an arm!"
Is AGI really imminent? Probably, but only to a specific and flawed definition. There is an important distinction. Intelligence is not a synonym or equal to competence. We are conflating intelligence with expertise and competence. This is a common problem in hyper-intelligent people.
These algorithms may well reach superhuman levels of intelligence. Does it matter? Regards actual expertise and output, they are mediocre at best.
To a beginner in any field, intermediate is impressive. Unparalleled speed alongside something that resembles (but is not equal to) competence has the effect that those who are starting in any field are in awe of this tool. They are the confident graduate, unknowingly ruining the professional competence of your business.
Full blog post about why I think GenAI is cracking nuts with a sledgehammer
I used ->
* Llama 3 (on Groq) * WebSpeechRecognition API * Deepgram (TTS)
Each individual system is comprehensive and reasonably mature, but glue them all together on our proverbial pig in lipstick and there is no real understanding of the nuances of audio interactions.
Shopify WebRTC audio/visual ecommerce marketplace
How to Leverage the AWS WebSocket API for Serverless WebRTC Signaling
Exactly, we have...
I wrote a little blog about it: https://yown.it/live-video-call-webrtc
If that doesn't explain it well enough I'll just assume you see being intentionally aggressive!
None of the above solutions enable users to easily manage personalized commerce experiences without paying a developer!!
WebRTC Video Calls Implemented in React
Given we allow anonymous connections, we need to associate each WebRTC connection with user defined data (read user profile). It's not quite as simple as "a cookie" because one user can have multiple devices, updated user information has to sync across the other connections and for a smooth experience you have to have synced connection statuses.
We did look at syncing all this with RTC data channels, problem... you can't get message history and you also can't depend on the channel until after a successful negotiation, which again for us is only part of the larger infrastructure...
This forces the use of a parallel comms system such as websockets, allowing for event based synchronisation as well as the organisation of the WebRTC metadata both pre and post connection...
Most people don't want "naked javascript" with two faces on it, and WebRTC is a fantastic tool for video and audio streaming, however it is limited in its wider use (which is perfectly fine it does enough!)...
I think the problem is that people associate "video chat" with simply the media streaming, whereas the reality is that integrating it into a feature rich front end framework is significantly more complicated, and not simply a case of "adding a cookie"
The difference between the solutions you posted and websockets is as far as I can tell, "your own websockets" or "pay someone else to run your websockets".
To stably build a negotiation system you'll probably need an infrastructure of websockets and some kind of nosql db to handle identity and other quirks around negotiation...
Example... how do you handle refresh from a new tab or after the connection has dropped... some kind of device signature is probably needed too!!
(We've just spent a year building this for ecommerce @ https://yown.it)
BIG thumbs up for the interest in WebRTC though enormous potential...