2,947 karma · joined March 3, 2019
It will take transparent MP4/MOV as input and output compatible versions for Safari (HEVC) and Chrome (WEBM). Then you simply use a tag that includes both e.g:
<video playsinline preload="metadata">
<source src="video.mp4" type="video/mp4; codecs=hvc1">
<source src="video.webm" type="video/webm">
</video>The code interpreter is running real code against the real files in the Linux environment OP posted, it's not hallucinating tokens at this point.
The worst names are the ones that you have to spell out, or have some weird character substitutions. It makes it hard to spread via word of mouth and find on search.
Bonus points if it's related directly to the product, but it can also be an abstract reference if that isn't possible.
Lastly, don't overthink or waste too much time on naming it. Spend time building a great product that solves a real problem and name it closer to launch if you're stuck.
I will caveat that though, I am bullish on Google and AI in general given the incredible talent and vast amount of data Google has access to. I think eventually they will make a technological breakthrough that puts them back in the leader position - they had it with transformers and just didn't know how to turn it into a product.
There is no problem with the chat UX, if you know the right techniques to get optimal output, but writing effective prompts is a technical skill similar to programming - most folks that interact with computers are not highly technical.
If we design software powered by LLMs understanding that effective prompting is a skill most users don't have, then we should build UX that abstracts prompting away. Of course there are going to be use cases where a user needs to provide input to the LLM, but that UX also can be assistive and require minimal cognitive overhead (e.g less raw text prompt input, more clicks on buttons/forms etc to a backend prompt builder).